implementation-planning

To convert a design document into a TDD implementation plan, apply the planning skill to your feature design file. It decomposes technical sections into 2–5 minute failing-test-first tasks and generates a traceability matrix mapping DR-N requirements.

Test-first task decomposition breaks technical design sections into granular 2–5 minute tasks. Each task begins with a failing test and includes expected failure reasons, ensuring no production code ships without corresponding tests.

Generate a spec traceability matrix by transforming design files into implementation plans. The process enforces DR-N provenance, mapping each design requirement to actionable tasks and running deterministic verification checks via orchestration.

Yes, the planning workflow detects independent task groups within a design document suitable for parallel worktrees. It manages phase transitions, updates workflow state, and handles revision loops with guardrails.

Yes, you need an existing design document file to use as input. The tool transforms existing feature or refactor design files into implementation plans, outputting a dated plan file with tasks and plan-review gating.

Automated plan verification relies on deterministic checks via orchestration actions. While it enforces failing-test-first TDD and guardrails for revision loops, complex or ambiguous design documents lacking clear DR-N requirements may limit verification accuracy.