tdd-workflow

The red-green-refactor cycle in Test-Driven Development involves writing a failing test, implementing minimal code to pass it, and then refactoring while ensuring tests remain green. This methodology improves code quality and maintainability from the outset.

To start a TDD workflow, signal the beginning of a new cycle using the tdd_phase tool, describing the behavior to be tested. The agent will then guide you through stubbing, writing minimal passing code, and performing an atomic commit.

Stubbing guidance during TDD is needed when creating failing tests for new behaviors. It teaches when and how to create stubs for validation, ensuring the test correctly fails for the right reasons before any actual implementation logic is written.

Yes, this TDD methodology enforces a commit cadence by promoting atomic commits for each completed red-green-refactor cycle. This ensures your development workflow maintains granular, logical version control increments tied directly to test validation.

The best way to refactor code while maintaining test coverage is to follow the TDD cycle: write failing tests, implement minimal passing code, and refactor only while ensuring tests remain green. This prevents regressions during agile development.