TDD Feature Development

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.

Defines a gated Research-Plan-TDD-Review-Commit pipeline for orchestrating feature development, defect fixes, and refactoring tasks through composable phases and human approval gates.

Guides implementing features and bug fixes test-first, enforcing red-green-refactor with mandatory failure verification.

Implements a feature phase by phase from a phased JSON or Markdown plan, with configurable unit-test and quality-gate choices per phase, token-budgeted execution, resumable state, and TDD handoff.

Refactors production code with test coverage using a TDD workflow that applies approved refactorings one at a time, gates each on passing tests, and commits or reverts accordingly.

Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predicting failures before every run, hardcoding minimum changes, and using triangulation and property-based testing. Triggers on explicit TDD requests and tasks phrased as 'implement', 'add', 'write a function', 'build a feature'.

Implements code features phase by phase from a JSON or Markdown plan, with configurable unit-test and quality-gate choices, token-budgeted execution, and resumable state.

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