Why does the skill require me to watch a test fail?

Watching a test fail (the RED phase) is the only way to prove the test actually verifies the intended behavior and isn't passing by accident or due to an incorrect implementation.

How does this skill handle bug fixes?

It requires writing a failing test that reproduces the bug first. Once the test fails for the expected reason, you write the minimal code to fix it, following the standard TDD cycle.

When should I skip TDD using this skill?

TDD should be used for all features and bug fixes. Exceptions are only permitted for throwaway prototypes, generated code, or configuration files, and usually require human partner approval.

What is the Iron Law in this TDD skill?

The Iron Law dictates that no production code may be written without a failing test existing first. If code is written before a test, it must be deleted and rewritten following the test-first approach.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: Kingly-Agency

byKingly-Agency

Security & Testing

Enforces a strict Red-Green-Refactor workflow to ensure all code is verified by failing tests before implementation.

About

This skill implements a rigorous Test-Driven Development (TDD) methodology within Claude, prioritizing behavior verification through the 'Iron Law' of testing. It guides users through the mandatory cycle of writing a failing test, verifying the failure, implementing minimal code to pass, and refactoring for cleanliness. By forcing the discovery of edge cases before implementation and prohibiting production code without a prior failure, this skill eliminates technical debt and ensures that your test suite provides genuine confidence in your software's behavior.

Key Features

Mandatory 'Verify RED' phase to prevent false-positive test results
Automatic detection and discouragement of 'tests-after' rationalizations
Minimalist code implementation focus to prevent over-engineering
Strict enforcement of the Red-Green-Refactor development cycle
0 GitHub stars
Comprehensive verification checklists for feature completion and bug fixes

Use Cases

Reproducing and fixing bugs by creating regression tests first
Implementing complex business logic where correctness is mission-critical
Safely refactoring existing codebases with verified test coverage

About

Key Features

Mandatory 'Verify RED' phase to prevent false-positive test results
Automatic detection and discouragement of 'tests-after' rationalizations
Minimalist code implementation focus to prevent over-engineering
Strict enforcement of the Red-Green-Refactor development cycle
0 GitHub stars
Comprehensive verification checklists for feature completion and bug fixes

Use Cases

Reproducing and fixing bugs by creating regression tests first
Implementing complex business logic where correctness is mission-critical
Safely refactoring existing codebases with verified test coverage