What problem does it solve? Turning a feature idea or requirements document into an actionable, reviewable implementation plan is time-consuming and error-prone. This Skill produces durable technical plans with clear scope boundaries, sequenced implementation units, and verifiable test scenarios, so execution can start confidently without re-inventing decisions. ## Core Features & Use Cases - Research-Grounded Planning: Runs parallel repo, learnings, and optional external best-practices research agents before structuring the plan, and reuses upstream brainstorm requirements documents as the source of truth. - Right-Sized Plan Depth: Classifies work as Lightweight, Standard, or Deep, then scales template sections, implementation units, and risk treatment accordingly. - Confidence Check & Deepening: Scores plan sections against quality checklists and dispatches targeted specialist agents to strengthen weak sections, with interactive accept/reject review of findings. - Non-Software Planning: Routes non-software tasks to a universal planning workflow producing itineraries, curricula, runbooks, or project plans. - Use Case: After brainstorming a new authentication feature, run the plan command to generate a dated plan file in docs/plans/ with implementation units, Given/When/Then test scenarios, and deferred open questions, then hand it directly to the work phase. ## Quick Start Ask the assistant to create an implementation plan for your feature, for example: plan the user authentication flow based on the requirements document in docs/brainstorms.
