slowdini

auditing-slow-powers-usage

Use only when a slow-powers developer explicitly asks for a post-session audit of how slow-powers skills were used during the session just completed. A manual diagnostic for people working ON slow-powers — never relevant to ordinary development tasks; do not auto-invoke.

evaluating-skills

Use when testing whether a new skill improves agent behavior, or when validating a change to an existing skill's language.

hardening-plans

Use right after you've drafted or revised an implementation plan and before you present it or start coding — a fresh-eyes review that catches placeholders, hallucinated file references, irrelevant steps, and coverage gaps before the user has to

investigating-bugs

Use when encountering any bug, test failure, build error, or unexpected behavior.

test-driven-development

Use when implementing any feature, refactoring, or writing a bugfix.

verifying-development-work

Use before claiming any task is complete, fixed, or passing, and before handing finished work back to the user.

working-in-isolation

Use when you're about to start changing files in a repository — code, docs, config, or content, whether a feature, bugfix, refactor, or docs/config update — to establish an isolated workspace so your work doesn't collide with existing or in-progress work.

writing-skills

Use when creating new skills or editing existing skills. Drafting only; see slow-powers:evaluating-skills for measuring whether the draft works.