tdd-workflow

Test-driven development follows a Red-Green-Refactor-Validate cycle: write a failing test first, implement minimal code to pass it, refactor for quality, then validate via automated checks. This Skill enforces that cycle for all business logic and use cases, eliminating guesswork and ensuring consistent code quality across feature development and bug fixes.

Integrate automated quality checks into every development cycle using structured TDD patterns. This Skill applies the Red-Green-Refactor-Validate workflow to feature implementation and refactoring, running final validation through make qa to catch issues before code reaches production.

TDD applies across all testable code: new features, bug fixes, and refactoring. This Skill governs the entire development lifecycle for business logic and domain code, ensuring every change—whether fixing a defect or improving structure—follows the same proven quality standards.

Begin by writing a failing test that describes the desired behavior, then implement minimal code to pass it. Follow the Red-Green-Refactor-Validate cycle, writing tests before logic. This Skill automates that workflow for use case development, with final validation through make qa ensuring quality.

Skipping TDD introduces quality risks and guesswork into development. This Skill enforces the mandatory Red-Green-Refactor-Validate cycle to prevent unmaintainable code, ensure consistent patterns across the codebase, and catch defects early through automated checks rather than discovering them later.

TDD is most effective for testable code: business logic, use cases, and domain code. This Skill focuses on those areas rather than infrastructure or configuration, ensuring the workflow applies where it adds the most value and quality impact.