tdd-workflow

Enforce test-driven development by applying a strict seven-step workflow that requires real test execution results before transitioning between phases, ensuring verified progress. This prevents unchecked assumptions by synchronizing scenario documents, test files, and checkbox updates.

Turn functional requirements into scenario documents by defining explicit acceptance criteria and test status gates before writing code. This scenario-driven approach ensures requirements are clearly established and proven correct through failing tests prior to minimal implementation.

The Red Green Refactor workflow is a failure-first development process that requires writing failing tests, producing minimal code to make tests pass, then refactoring while preserving behavior. It drives the workflow from intent discovery to regression-safe final review.

Run regression tests after refactoring by executing the full test suite to verify that existing behavior is preserved. The workflow requires running these tests to confirm that refactoring did not introduce regressions before final review.

You can use this TDD workflow for implementing new API endpoints or domain rules because it handles new feature implementation by defining scenarios clearly and proving correctness with tests. It ensures you avoid merging code that only seems correct.

Scenario doc counts and test file counts need synchronization to maintain invariants that prevent hallucinated progress. This strict requirement ensures that every scenario document has a corresponding verified test file reflecting real test execution results.