What problem does it solve? Jumping straight from a feature idea to code often produces misaligned implementations, missed edge cases, and untested assumptions. This Skill enforces a structured plan-before-code workflow where requirements are critiqued, questions are answered, and a testable plan is approved by a human before any code is written. ## Core Features & Use Cases - Two human approval gates: Gate 1 requires the user to answer clarifying questions written into the requirements file; Gate 2 requires an explicit "approved" or "accepted" before implementation begins. - Opinionated approach analysis: Appends strengths, risks, gaps in the requirements, alternative approaches, and a defended recommendation directly to the requirements file on disk. - Traceable plan documents: Writes plans to /_plans/<feature>-plan.md with stable IDs for invariants (INV-n), tasks (P1.1), and tests (T-n), plus a coverage rollup mapping every requirement to a test. - Use Case: A user says "I want to build CSV export for the dashboard." The Skill creates /_reqs/csv-export.md, appends an analysis and clarifying questions, waits for answers, writes a phased plan with test definitions, and only implements after the user replies "approved". ## Quick Start Ask the assistant to plan and implement a new feature by describing it in chat or pointing to a requirements file, for example: "Use feature-planning to plan and build the CSV export feature described in /_reqs/csv-export.md."
