feature-delivery

To choose the right workflow discipline, evaluate the nature of the change to select standard, TDD, or refactor mode. This ensures the delivery process matches the required verification and safety nets for the specific code modification.

The Iron Law of TDD enforces strict red-green-refactor cycles during feature delivery. It mandates writing failing tests first, implementing minimal code to pass, and then refactoring, ensuring robust verification before completion.

Apply TDD planning to refactoring by using the refactor workflow mode, which relies on existing safety nets. You verify behavior before and after changes, ensuring minimal scope modifications without altering external functionality.

You can use the standard workflow for feature verification, but it is best suited for changes not requiring strict TDD. Complex changes may need TDD or refactor modes to ensure adequate safety nets and thorough verification checks.

Avoid standard mode and switch to refactor workflow when the code change involves restructuring existing internal logic without altering external behavior. The refactor mode provides specific verification checks and safety nets suited for structural improvements.

The best way to document structured handoffs is to use the documented outputs generated by the workflow. This provides traceability by recording the selected mode, verification checks, and completion status before passing the code change downstream.