tdd

Test-driven development discipline is enforced by automating red/green/refactor cycles with explicit phase prompts. This prevents test-then-implementation shortcuts and maintains one-behavior-per-cycle focus across feature development.

The red-green-refactor workflow drives feature design by writing a failing test first, implementing minimal code to pass it, then improving the design. This cycle keeps development focused on tests first and incremental improvement.

To prevent writing implementation before tests, the workflow enforces one-behavior-per-cycle discipline and blocks test-then-implementation shortcuts. It coordinates phase tracking to ensure tests always precede code.

You can automate test execution during the refactor phase using automatic test hooks. These hooks trigger test execution whenever test files change, ensuring tests stay green while you improve the code design.

You need plan mode to explore test strategy and track red/green/refactor cycles effectively. It provides the environment to design tests before implementation and coordinate phase tracking across features.

Strict red-green-refactor cycles may not suit exploratory prototyping or spike testing where immediate implementation is needed. The one-behavior-per-cycle discipline is designed for structured feature development, not unstructured experimentation.