tdd-red-green-refactor

To enforce strict test-driven development discipline, you must maintain a failing test in .tdd-state.json before writing any production code. This ensures verifiable, test-first progress across implementation tasks by guiding structured validation through logs.

The red green refactor workflow in TDD requires writing a failing test first, implementing minimal production code to pass it, and then cleaning up the design. This structured cycle prevents over-engineering and ensures verifiable progress tracking.

You track TDD state and log implementation results by updating .tdd-state.json and the 05-implementation-log.md file. This maintains an auditable progress history and documents the outcomes of each development phase.

Yes, you need a failing test before writing production code in Phase 4. The workflow requires maintaining a failing test state to prevent guesswork and ensure strict test-first development readiness across all tasks.

The four phases of TDD implementation are red, green, refactor, and simplify. You begin by writing a failing red test, implement minimal code to pass it, clean up the design, and log the results.

You prevent guesswork during Phase 4 task implementation by enforcing red/green/refactor discipline and tracking state in .tdd-state.json. This structured validation ensures verifiable progress and test-first readiness for every task.