tdd

Apply test-driven development cycles with requirements.md and test-runner agents.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/sizukutamago/claude-code-harness --skill tdd-sizukutamago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/sizukutamago/claude-code-harness/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/sizukutamago/claude-code-harness --skill tdd-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a test-first development workflow to prevent unverified code, regressions, and ambiguous behavior during new feature work, bug fixes, and behavior-changing refactors.

Core Features & Use Cases

  • Enforced TDD cycle: Requires writing a failing test (RED), implementing the minimal code to pass (GREEN), and then refactoring while keeping tests green.
  • Agent orchestration: Specifies dispatch to implementer and test-runner agents and prescribes structured status reports (DONE / DONE_WITH_CONCERNS / NEEDS_CONTEXT / BLOCKED).
  • Requirements-driven execution: Demands identification and use of an approved requirements.md (REQ path) and prompts the human partner when multiple candidates exist.
  • Use case: Implement a new feature from requirements/REQ-001 by driving the RED→GREEN→REFACTOR loop and verifying the full test suite passes before completion.

Quick Start

Identify the appropriate requirements.md for the task and dispatch the implementer agent to execute the RED→GREEN→REFACTOR cycle while ensuring tests fail first and then pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce a strict test-driven development workflow for new feature implementation?

Test-driven development is enforced by running a strict RED→GREEN→REFACTOR cycle, requiring a failing test before implementation and verifying the full test suite passes after minimal code changes.

What is the best way to drive code implementation from approved requirements during behavior-changing refactors?

Requirements-driven execution identifies and uses an approved requirements.md file, prompting for selection when multiple candidates exist to ensure implementation matches expected behavior.

Can I use agent orchestration to automate the test-first TDD cycle and test suite verification?

Agent orchestration dispatches implementer and test-runner agents to execute the test-first TDD cycle and verify the full test suite, returning structured status reports like DONE or BLOCKED.

How does test-driven development prevent unverified code and regressions during bug fixes?

Test-driven development prevents regressions by mandating a failing test first, implementing minimal passing code, and refactoring only while keeping the full test suite green.

Do I need an approved requirements.md file before starting test-driven development?

An approved requirements.md file is required before starting, ensuring a clear requirements path and human partner approval are available to drive the test-first implementation.