10x-tdd

Automating test-first development requires sequentially executing TDD steps for each phase in an approved technical plan. This Skill drives the red, green, refactor cycle automatically, ensuring production code is only written to pass a pre-existing failing test.

Executing TDD implementation phase by phase is fully supported. You provide a change-id and phase number, and the Skill sequentially writes a failing test first, then implements the production code to pass it for that specific phase.

An existing test infrastructure is required to run test-driven development phases. The Skill automates the red, green, refactor cycle but relies on your pre-existing setup to execute tests and validate the production code implementation.

To ensure a phase is TDD-ready, the Skill performs a TDD-ability check before writing any test. It verifies if the phase can be meaningfully driven by a failing test and confirms no current production implementation exists for that phase.

You should not use automated test-first execution for phases that already contain production implementation. The Skill is strictly applicable only to phases without existing production code to maintain pure test-driven development integrity.

TDD phase execution formats commit messages automatically using the Conventional Commits style. This ensures your version control history remains consistent as you progress through each test-first implementation phase.