tdd

Guide teams through red-green-refactor loops with behavior-focused tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams build reliable software by guiding development through a red-green-refactor loop, ensuring tests validate behavior rather than implementation.

Core Features & Use Cases

  • Red-Green-Refactor workflow: Drive design and confidence by cycling through failing, passing, and refactoring with public interfaces.
  • Vertical slices & incremental practice: Emphasize small, end-to-end slices that verify user-facing behavior.
  • Use cases: Apply to feature development and bug fixes, with tests guiding architectural decisions.

Quick Start

Start a tracer-bullet cycle by writing one end-to-end test that fails, then implement just enough code to pass it.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I use the red-green-refactor loop to drive feature development?

The red-green-refactor loop drives feature development by writing a failing test, implementing just enough code to pass it, and then refactoring to improve design while maintaining test confidence.

What is test-driven development behavior-focused testing?

Behavior-focused testing validates software behavior through public interfaces rather than internal implementation, ensuring tests guide architectural decisions and remain resilient during refactoring.

How do I start a tracer-bullet cycle for incremental feature work?

Start a tracer-bullet cycle by writing one end-to-end test that fails, then implementing just enough code to pass it, verifying user-facing behavior in small vertical slices.

Can I apply test-first discipline to bug fixes and feature experiments?

Test-first discipline applies to bug fixes and feature experiments by using failing tests to shape design across public interfaces and verify incremental improvements before implementation.

Does test-driven development work for incremental projects without existing tests?

Test-driven development suits incremental projects without existing tests by emphasizing small, end-to-end vertical slices that verify user-facing behavior and guide architectural decisions progressively.

When should I avoid test-driven development for software quality?

Avoid test-driven development when implementation details are unstable or when public interfaces are undefined, as behavior-focused tests require clear architectural boundaries to guide design effectively.