When should I avoid using the TDD workflow?

TDD is less effective for exploratory spikes, UI styling, one-off scripts, or throwaway prototypes where the architecture is not yet defined.

How does the TDD skill implement the development cycle?

The skill follows the classic Red-Green-Refactor rhythm: first, it defines expected behavior with a failing test (RED); second, it implements the minimal code necessary to pass (GREEN); and third, it cleans the implementation while verifying the tests still pass (REFACTOR).

Does this skill support the testing pyramid?

Absolutely. It encourages a balanced approach with many fast unit tests at the base, followed by integration tests, and a minimal set of expensive E2E tests at the top.

Can I use this skill for legacy codebases?

Yes, it incorporates Michael Feathers' techniques for working with legacy code, focusing on writing characterization tests to create a safety net before attempting to refactor or add features.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: primeinc

byprimeinc

Security & Testing

Guides Claude through the Red-Green-Refactor cycle to ensure robust, well-designed, and maintainable code.

About

The TDD skill empowers Claude to follow industry-standard testing methodologies, drawing from the philosophies of software pioneers like Kent Beck and Michael Feathers. It facilitates a disciplined development cycle where tests define behavior before implementation, resulting in executable documentation and significantly higher code confidence. By balancing rigorous testing with architectural counterpoints from experts like John Ousterhout, this skill helps developers avoid regressions, manage legacy codebases, and maintain high-quality software through systematic refactoring and ergonomic API design.

Key Features

Advanced testing patterns including Triangulation and 'Fake It Til You Make It'
Balanced design guidance to prevent over-testing implementation details
0 GitHub stars
Integrated workflow management using beads for task tracking
Red-Green-Refactor workflow automation
Legacy code characterization and stabilization techniques

Use Cases

Developing new features with strict requirements and verifiable behavior.
Reproducing and resolving bugs by creating failing test cases first.
Safely refactoring complex logic in legacy systems with a protective test suite.

About

Key Features

Advanced testing patterns including Triangulation and 'Fake It Til You Make It'
Balanced design guidance to prevent over-testing implementation details
0 GitHub stars
Integrated workflow management using beads for task tracking
Red-Green-Refactor workflow automation
Legacy code characterization and stabilization techniques

Use Cases

Developing new features with strict requirements and verifiable behavior.
Reproducing and resolving bugs by creating failing test cases first.
Safely refactoring complex logic in legacy systems with a protective test suite.