tdd-workflow

Test-driven development follows the red-green-refactor cycle by writing a failing test first, implementing minimal production code to pass it, and refactoring for readability. This skill codifies that workflow into structured phases for disciplined testing.

Core TDD rules include writing tests before production code, maintaining one assertion per test, and keeping changes small. These practices ensure reliable, maintainable software by enforcing incremental progress and explicit testing standards.

The TDD workflow applies across feature development, bug fixes, and exploratory work. It guides test-first practice in each scenario, ensuring minimal production code and incremental refactoring regardless of the task type.

Starting test-first in an agile workflow requires writing a failing test that captures desired behavior, then implementing the minimum code to pass it, and finally refactoring. This skill provides repeatable phase-based guidance to ensure consistent execution.

TDD workflows break down during refactoring when changes are too large or tests lack behavior-oriented naming. This skill prevents breakdown by enforcing small changes, one assertion per test, and clear phase transitions between green and refactor.