Use when you have a spec or requirements for a multi-step task, before touching code
Use when you have a written implementation plan to execute in a separate session with review checkpoints
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when picking up a user-gate task OR when a hook demands re-validation. Runs the "do I know HOW?" self-check; if the HOW is clear, executes the verification and posts evidence; if not, hands off to specifying-gates. Kept deliberately separate from…