implement-feature

TDD green phase involves writing the minimum code required to make failing tests pass. You apply the highest-priority transformation available to satisfy tests, then run the suite to verify the green state without modifying locked test files.

The Transformation Priority Premise in test-driven development provides a defined priority list of deterministic code transformations. It guides the selection of the simplest change needed to make failing tests pass, ensuring minimal and reviewable code evolution.

To enforce minimal changes across feature slices when test files are locked, apply the highest-priority TPP transformation available and run tests after each change. A reviewer validates the transformation rationale, ensuring only approved changes are accepted into the green state.

No, you cannot modify test files during TDD green phase implementation. Test files are locked and cannot be edited; the process strictly focuses on implementing the minimum production code required to make the existing failing tests pass.

A reviewer is needed in TDD green phase to validate your transformation choices upon completion. This review-driven progress captures the rationale and verifies the exact changes made, ensuring only approved transformations are accepted into the green state.

The best way to track transformation history during TDD green phase is to record the exact changes made at each step. The system captures the rationale and shows the exact transformation path taken to achieve the approved green state.