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 receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Guide a user through the full idea-to-product pipeline from initial idea through strategy, product, architecture, delivery, and outcome review; choose the next step from state, invoke the matching P1-P10 skill, request gates when needed, and keep the user oriented.
Capture a real product or business idea as a falsifiable hypothesis, clarify the user, frequency, quantified loss, workaround, urgency, do-nothing cost, risks, and stop conditions, then initialize assumptions and risks for downstream strategy work. Use when the user explicitly asks for idea2product-P1-idea-expansion, P1, phase 1, or this step of the idea-to-product pipeline.