Can I use this skill for bug fixes?

Yes, it is highly recommended for bug fixes to ensure the specific issue is reproduced by a failing test before the fix is implemented.

Why does this skill require test output evidence?

Evidence ensures that the test actually failed for the expected reason and subsequently passed, preventing false positives and ensuring the test truly verifies the code's behavior.

What is the 'Iron Law' in this TDD skill?

The Iron Law dictates that no production code can be written without a failing test first; if code is written early, it must be deleted and started over.

What happens if I write code before the test?

The skill protocol mandates that you must delete the implementation and start fresh from the testing phase to ensure the test is not biased by existing code.

Does this skill support different testing frameworks?

Yes, it is designed to work with any command-line testing tool including npm test, pytest, cargo test, and others by capturing their standard output.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: bacchus-labs

bybacchus-labs

•

Security & Testing

Enforces a rigorous Red-Green-Refactor workflow by requiring mandatory failing tests and execution evidence before any production code is written.

About

The Test-Driven Development (TDD) skill for Claude Code transforms the development process into a disciplined, verification-first workflow. It operates on the 'Iron Law' that no production code exists without a preceding failing test, ensuring that every feature and bugfix is validated by evidence rather than assumptions. By mandating the Red-Green-Refactor cycle and requiring real-time terminal output as proof of verification, this skill eliminates technical debt, prevents regressions, and produces self-documenting codebases that are highly resilient to change.

Key Features

Logic-driven TDD cycle flow for consistent implementation patterns
Standardized TDD compliance certification for new functions
Strict enforcement of the Red-Green-Refactor cycle
Mandatory terminal output evidence for test failure and success
3 GitHub stars
Standardized skill usage announcements for session auditing

Use Cases

Implementing new features with high-confidence behavior verification
Resolving complex bugs by isolating the failure with a test case first
Safe refactoring of legacy systems while maintaining behavioral parity

About

Key Features

Logic-driven TDD cycle flow for consistent implementation patterns
Standardized TDD compliance certification for new functions
Strict enforcement of the Red-Green-Refactor cycle
Mandatory terminal output evidence for test failure and success
3 GitHub stars
Standardized skill usage announcements for session auditing

Use Cases

Implementing new features with high-confidence behavior verification
Resolving complex bugs by isolating the failure with a test case first
Safe refactoring of legacy systems while maintaining behavioral parity