What problem does it solve? Turning a finished product specification into an executable, phase-by-phase development plan is error-prone: phases get misordered, dependencies break, and tasks end up as vague placeholders. This Skill analyzes Product-Spec.md and Design-Brief.md, verifies technology choices via web search, and outputs a concrete DEV-PLAN.md that a builder agent can execute phase by phase. ## Core Features & Use Cases - Phased Plan Generation: Builds a dependency graph (DAG) from spec features, topologically sorts it, and splits work into independently verifiable phases, each with deliverables, key file paths, and acceptance criteria. - Tech Stack Verification: Uses web search to confirm framework versions, compatibility, and breaking changes before committing to a stack, offering 2-3 options when multiple reasonable choices exist. - Iterative Plan Updates: After spec changes, identifies affected phases, updates DEV-PLAN.md without touching completed phases, and flags when dev-builder needs to resync implemented code. - Use Case: You have a completed Product-Spec.md for a chat application. Run this Skill to produce DEV-PLAN.md with phases like "SQLite persistence + message CRUD" and "chat UI with streaming", each listing exact files to create and acceptance criteria. ## Quick Start Read Product-Spec.md and Design-Brief.md in this project and generate a phased DEV-PLAN.md with verified tech stack, dependency-ordered phases, key files, and acceptance criteria.
