test-driven-development

To enforce the Red-Green-Refactor cycle, you must write a failing test before any production code. This discipline is guided by requiring a failing test first, then implementing minimal code to pass, and preventing early refactoring before tests pass.

Test-driven development workflow integration connects feature implementation with the workflow plugin to automatically generate, run, and validate tests. This ensures the Red-Green-Refactor process is strictly followed from writing a failing test to the final refactor.

To start a new feature using TDD discipline, trigger the workflow via the /tdd:start command or mention test cues. This initiates the process by requiring a failing test before you write any production code.

No, you cannot refactor code before tests pass in TDD. Guardrails and feedback prevent early refactoring, ensuring you only enter the refactor phase after your minimal production code successfully passes the failing test in the Green stage.

The TDD workflow integrates with the workflow plugin to generate and validate tests, but requires no external dependencies. It operates independently to enforce the Red-Green-Refactor cycle during feature implementation.

Writing a failing test before production code ensures the test actually validates the new feature. This TDD discipline guarantees code quality by enforcing the Red-Green-Refactor cycle and preventing early refactoring before tests pass.