Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when the user invokes /spec, says "create a spec", "write a spec", "let's build X", "I want to add a feature", or when starting any feature work — both exploratory and well-defined tasks
Use when executing implementation plans with independent tasks in the current session
Use when you have a spec or requirements for a multi-step task, before touching code
Use when the user invokes /compound, says "capture learnings", "what did we learn", or when suggesting post-cycle knowledge capture after completing a development branch
Use when starting a session, generating specs or plans, reviewing code, or when the user asks about company coding standards, architecture patterns, security requirements, or testing conventions