plan-implementation-coder

Converting an architecture document into TDD code requires reading the design doc, sequencing work by dependency constraints, and delegating RED-GREEN-REFACTOR cycles to generate tested code per step.

Doc-driven development with deviation tracking maintains a stable high-level architecture doc and an evolving low-level design doc, recording meaningful deviations to prevent silent drift between code and documentation.

You orchestrate step-by-step implementation from a design doc by using a non-interactive sub-skill mode, supplying the design-doc path to coordinate per-step execution across components without manual intervention.

Yes, the TDD workflow includes pre-commit review gates by running RED→GREEN→REFACTOR cycles, performing a self-review aligned to specific KPIs, and running pre-commit verification to prevent test and build regressions.

Yes, you can execute architecture-to-code generation component by component by applying controlled execution per step or per component, sequencing the work based on dependency constraints outlined in the design document.

A limitation of using a static architecture document for implementation planning is that it cannot silently drift; meaningful deviations from the evolving low-level design must be manually recorded to maintain doc consistency.