Skill

tdd

Guides test-driven development (TDD) for new features, bug fixes, and behavioral changes. Write failing tests first, implement minimally to pass, then refactor.

testing

npx claudepluginhub owainlewis/blueprint --plugin blueprint

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- New logic or behavior

SKILL.md

Similar Skills

test-driven-development

Enforces Test-Driven Development: write failing tests first, then minimal code to pass, refactor. For implementation tasks, bug fixes needing regression tests, behavior changes.

1 file

superpowers-optimized

tdd

Enforces TDD red-green-refactor cycle: failing test first (RED), minimal passing code (GREEN), refactor. For features, bugfixes, refactoring. Language-agnostic.

jig

test-driven-development

142

Enforces strict Test-Driven Development (TDD): write failing test first for features, bug fixes, refactors before any production code.

hive

Stats

Stars79

Forks18

Last CommitApr 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Test-Driven Development

When to use

New logic or behavior

Bug fixes

Changes that could break existing behavior

Process

Understand the requirement and the relevant code.

Write a failing test for the behavior you want.

Write the minimum code needed to make the test pass.

Simplify the code and tests while they stay green.

Run the full relevant test suite before finishing.

Verification

The new behavior has a failing-then-passing test

Bug fixes include a reproduction test

Tests describe behavior, not implementation details

The final test suite passes

Rules

Make the smallest safe change that satisfies the failing test.

Preserve existing contracts unless the task explicitly changes them.

Add tests for failure paths when they matter to the behavior.

Do not write implementation code before you have a failing test for the behavior.

Skip TDD for documentation, formatting, or non-behavioral scaffolding work.

Prefer testing behavior over internals.

Use mocks sparingly. Prefer real boundaries when practical.

Test-Driven Development

When to use

New logic or behavior
Bug fixes
Changes that could break existing behavior

Process

Understand the requirement and the relevant code.
Write a failing test for the behavior you want.
Write the minimum code needed to make the test pass.
Simplify the code and tests while they stay green.
Run the full relevant test suite before finishing.

Verification

The new behavior has a failing-then-passing test
Bug fixes include a reproduction test
Tests describe behavior, not implementation details
The final test suite passes

Rules

Make the smallest safe change that satisfies the failing test.
Preserve existing contracts unless the task explicitly changes them.
Add tests for failure paths when they matter to the behavior.
Do not write implementation code before you have a failing test for the behavior.
Skip TDD for documentation, formatting, or non-behavioral scaffolding work.
Prefer testing behavior over internals.
Use mocks sparingly. Prefer real boundaries when practical.