tdd-enforce

Test-driven development enforces writing failing tests before implementation, then coding the minimum solution to pass each test. This workflow—Red-Green-Refactor—catches bugs early, improves reliability, and ensures every feature is validated by tests before deployment.

Red-Green-Refactor is TDD's core loop: write a failing test (Red), implement minimal code to pass it (Green), then clean up the code (Refactor). Repeat for each feature piece. This disciplined approach breaks large tasks into small, verifiable steps and prevents regressions.

Yes, TDD naturally breaks complex features into small, manageable test-code pairs. Each test defines one requirement; implementing to pass that test isolates work into discrete, verifiable units. This makes large projects easier to track and reduces integration risks.

Apply TDD when planning feature implementation, during TodoWrite planning sessions, or when explicitly targeting test-first approaches. It's most valuable for complex logic, shared code, and projects prioritizing code reliability and maintainability.

Yes, TDD guarantees each code unit passes its test before proceeding, eliminating untested code. Tests validate behavior upfront, catch edge cases early, and create living documentation. This discipline significantly reduces bugs and regression risk.

TDD prevents bugs by requiring tests before code exists—you define expected behavior explicitly before implementation. Tests catch logic errors, boundary conditions, and side effects immediately. Refactoring with a passing test suite ensures changes don't break existing functionality.