tdd

Automate test-driven development workflows with red-green-refactor cycles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) helps teams validate desired behavior by writing tests before implementing features, reducing regressions and guiding clean design.

Core Features & Use Cases

  • Red-Green-Refactor loop: write a failing test, implement just enough code to pass, and refactor safely.
  • Tracer-bullet driven development: drive design and implementation incrementally, one test at a time.
  • Integration-style testing focus: verify workflows through public interfaces rather than internal details.

Quick Start

Describe a feature by writing a failing test first, then implement only what's needed to make it pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I implement features using test-driven development?

Test-driven development implements features through a red-green-refactor loop: write a failing test, implement just enough code to pass, then refactor safely to minimize regression risk.

What is vertical slicing in TDD?

Vertical slicing in TDD drives design and implementation incrementally, verifying complete workflows through public interfaces rather than testing internal implementation details.

How do I write integration tests for public interfaces?

Integration tests for public interfaces verify software workflows through external behavior, enforcing reliable functionality without coupling tests to internal system details.

When should I use refactoring during the TDD cycle?

Refactoring occurs during the green phase of TDD, applying incremental design improvements after tests pass to safely minimize regression risk without changing behavior.

Does test-driven development work for bug fixes?

Test-driven development guides bug fixes by first writing a failing test that reproduces the defect, then implementing the minimal code correction needed to make it pass.

Why do my tests keep breaking when I refactor internal code?

Tests break during refactoring when they rely on internal details; enforcing public-interface tests and vertical slicing prevents this coupling and minimizes regression risk.