code-implementer

To translate a design plan into production-ready code, provide the ARCH or PLAN document to enforce a TDD-first workflow, iterating from a failing test to passing code with minimal changes.

A TDD-first workflow for implementing features requires starting with a failing test, writing just enough code to pass, and refactoring while keeping tests green to ensure verifiable software changes.

Yes, you need an architecture document like ARCH, PLAN, or README to define feature scope and boundaries before starting the TDD cycle to ensure the implementation aligns with the design.

Yes, you can implement both backend and frontend components using TDD, as the process applies stack-aware loading to read backend or frontend references on demand and align with your stack.

To ensure minimal code changes during feature implementation, follow a strict test-driven development cycle that enforces writing only enough code to pass tests before refactoring.