code-implementer

To turn a design document into production-ready code, this skill reads a completed DESIGN.md and translates it into a phased implementation plan with defined tasks, security gates, and test stubs for task-by-task execution across phases.

Phased implementation breaks down a design document into sequential execution phases with defined inputs, outputs, and dependencies. This approach enforces phase gates and spec compliance to minimize rework and risk during code production.

In a design-to-code workflow, test-driven development is enforced by generating test stubs for each task within the implementation phase. This ensures spec compliance and maintainability before the actual code execution proceeds.

Yes, a completed DESIGN.md file is required to start automated code implementation. The skill applies when the design document exists and uses it to generate the phase plan defining tasks, gates, and security checks.

Security gates are enforced during code implementation by integrating them directly into the phase plan. The skill checks spec compliance and security requirements at each phase gate before allowing the implementation to proceed to the next task.