Ship Feature with TDD

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Delivers changes incrementally by building in thin vertical slices, testing and verifying each piece before moving to the next.

Drive development with tests by writing a failing test before implementing code, and reproduce bugs with tests before fixing them.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Guides the red-green-refactor cycle for implementing features with test-driven development, including test quality guidelines, framework setup, and commit patterns.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests when writing features, fixing bugs, or refactoring code.