tdd

Guide developers through red-green-refactor cycles for features and bug fixes.

23|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/reedmayhew18/ClawedBack --skill tdd-reedmayhew18
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/reedmayhew18/ClawedBack/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/reedmayhew18/ClawedBack --skill tdd-reedmayhew18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development workflow helps teams implement features or fix bugs with a red-green-refactor cycle, ensuring code quality and regression safety.

Core Features & Use Cases

  • Step-by-step TDD process: write failing tests, run them to see red, implement code to pass, refactor, and iterate.
  • Guidance for mutation-resistant assertions and test placement.
  • Use case: when adding a new feature, or fixing a bug, use TDD to drive design and prevent regressions.

Quick Start

Describe the feature or bug, write failing tests first, run the tests to see red, and implement the code until all tests pass.

Frequently Asked Questions about tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start test-driven development when adding a new feature?

Test-driven development is a red-green-refactor cycle where you write failing tests, implement code to pass them, and refactor. It drives software design and prevents regressions when adding features or fixing bugs.

How do I write mutation-resistant tests for my codebase?

Write mutation-resistant tests by applying explicit guidance for assertion strength and test placement. This ensures your tests catch logic errors rather than just verifying execution paths.

What do I need to run a red-green-refactor workflow?

You need a test runner and an existing codebase to run a red-green-refactor workflow. Explicit guidance then enforces the discipline required to iterate through failing tests, implementation, and refactoring.

When should I use TDD instead of writing tests after implementation?

Use TDD instead of writing tests after implementation when adding new features or fixing bugs to actively drive software design. This approach ensures regression safety and higher software quality through upfront test creation.