tdd-workflow

Test-first development enforces writing tests before implementation code. This Skill guides you through the Red-Green-Refactor cycle: write failing tests first (Red), implement minimal code to pass them (Green), then refactor while keeping tests passing. It auto-starts the workflow and includes pytest-based checks with Ruff linting and MyPy type validation.

Red-Green-Refactor is a TDD pattern: Red (write a failing test), Green (write minimal code to pass it), Refactor (improve code quality without breaking tests). Use it when starting new features, fixing bugs, or refactoring existing code. This Skill enforces the full cycle to maintain code quality and test coverage throughout development.

Yes. This Skill implements a pytest-based workflow that integrates Ruff for linting and MyPy for type checking. It follows test-file conventions like tests/test_<name>.py and runs quality gates after tests pass, ensuring code meets both functional and static analysis standards.

This Skill enforces test-file conventions matching your implementation files—for example, tests/test_<name>.py for src/<name>.py. It guides test creation before implementation and requires explicit approval before advancing phases, ensuring intentional test design and coverage.

TDD works best for feature development, bug fixes, and refactoring where requirements are clear. It may slow initial exploration or prototyping. This Skill requires an explicit approval gate between phases; teams must commit to the discipline for it to be effective.

This Skill applies to new features, bug fixes, and refactoring equally. For any task, it guides test creation first, ensures tests pass, then validates code quality. The Red-Green-Refactor cycle maintains existing test coverage while improving or fixing code.