implementation-plan

Implementation planning transforms PRD and SDD documents into step-by-step executable tasks by applying a structured PLAN template with phase-based sequencing, test-driven cycles (Prime → Test → Implement → Validate), explicit task metadata, and traceability back to source specifications.

The PLAN template prescribes TDD phases for each execution block: Prime (setup), Test (validation criteria), Implement (core work), and Validate (gate checks). Each phase maps to specific tasks with dependencies, owners, and links to PRD/SDD requirements.

Embed specification references directly in task metadata within implementation-plan.md, mapping each task phase back to its originating SDD or PRD section. This creates a queryable chain from high-level requirements through validation gates.

Yes. The Skill applies to creating new PLAN documents from scratch, completing individual phases in existing implementation-plan.md files, and defining task sequences across multiple docs/specs without requiring full project restart.

Each phase includes explicit validation gates: test coverage requirements after Test phase, acceptance criteria verification after Implement phase, and integration checks after Validate phase. Gates prevent task progression until dependencies and quality thresholds are met.

The template guides TDD structure for those new to the practice. It prescribes the cycle sequence and task metadata format, though understanding TDD principles (test-first, iterative validation) helps apply the phases effectively.