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 you have a TDD plan from writing-tdd-plans with triplet tasks (RED/GREEN/REVIEW) and dependency graph, ready for execution
Use when you have a design document and need to create an implementation plan with enforced TDD and adversarial review gates per task
Use when you have a complex design document where feature decomposition has multiple valid approaches, unclear dependencies, or architectural tradeoffs that benefit from adversarial debate before creating a TDD plan
Use when test suite needs cleanup, when tests are brittle or break on refactors without behavior change, when there are tests coupled to implementation details, or when test maintenance burden is high
Use when reviewing code changes on the current branch, before merging or creating a PR, or when asked to do a code review
Generate codebase specs (semantic) for comprehensive project documentation
Use when creating new skills, editing existing skills, or verifying skills work before deployment