implementation-planning

To translate requirements into structured implementation plans, use a template-driven approach to generate executable tasks with clear deliverables, sequencing work and mapping dependencies. This ensures high-level project specs become actionable development steps.

TDD-driven task breakdown for implementation planning is a workflow that enforces Prime, Test, Implement, and Validate cycles. This cycle sequence ensures every generated task remains verifiable and directly testable against the project requirements.

You can create an implementation plan from a PRD by applying explicit validation gates against the document. The skill uses your PRD and SDD to structure tasks, mapping dependencies and deliverables directly into an implementation-plan.md file.

Implementation planning requires no external dependencies or components to function. It operates independently using a template-driven approach to write the plan directly into your docs/specs/ directories without needing additional software libraries.

The best way to map dependencies and sequence work is through automated task breakdown that applies explicit tracking of dependencies and deliverables. This approach validates sequencing against your PRD and SDD before implementation begins.

You should use template-driven implementation plans instead of manual task breakdown when transforming complex project specs into executable tasks. It provides explicit gating against PRD and SDD documents, ensuring verifiable deliverables through TDD cycles.