Shape a codebase's architecture, at the start or once it fights you. Use when setting up a new codebase or area, choosing structure and conventions, or when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled…
Find the root cause of a bug before fixing it. Use whenever the user says "fix", "broken", "not working", "error", "failing", or "bug", and whenever a bug, test failure, or unexpected behavior appears, before proposing any fix.
Full ceremony mode for the whole suite. Run /deep before risky or ambiguous work; /deep off returns to fast-first.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, drill into their design, or says "drill this" or "drill me".
Implement a settled plan test-first, smallest slice at a time. Use when starting implementation of a feature or fix after the plan is settled, or when user says "implement this" or "build it".
Finish a development branch. Use when implementation is complete and the work needs to be merged, pushed as a PR, kept, or discarded.
Build a throwaway UI prototype to react to before committing. Use when a design fork turns on look, feel, or flow that prose cannot settle, or when the user asks to prototype or mock something up. Prefers the /design canvas; falls back to a self-contained…
Gate a taste claim that no command can prove, such as "this API design is good" or "this UI is not slop", by judging the work against checkable criteria. Use when verify meets a claim its commands cannot settle, when a design or artifact needs a quality call…