tdd

Execute red-green-refactor TDD cycles for feature development and bug fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development helps teams guarantee behavior by writing tests that describe public interfaces before code, reducing regressions and enabling safer refactors.

Core Features & Use Cases

  • Planning and early validation through red-green-refactor cycles.
  • Tracer-bullet incremental development with vertical slices.
  • Emphasis on integration-style tests and public interfaces to protect implementation details.

Quick Start

Write one failing test, implement only enough code to pass, then repeat.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I start writing tests first using red-green-refactor cycles?

Test-driven development drives feature work by writing a failing test that defines a public interface, implementing only enough code to pass it, then refactoring safely. This red-green-refactor cycle reduces regressions and enables iterative refinement during feature creation and bug fixes.

What is the best way to structure integration testing for vertical slices?

Structure integration testing around vertical slices using tracer-bullet development. Emphasize integration-style tests that validate public interfaces end-to-end, protecting implementation details while progressively disclosing guidance through incremental development loops.

Does test-driven development work for fixing bugs in existing codebases?

Yes, test-driven development applies to bug fixes in codebases requiring end-to-end test-first discipline. Write a failing test that reproduces the bug against the public interface, implement the fix to reach green, then refactor to satisfy iterative refinement requirements.

How does emphasizing public interfaces improve software design during refactoring?

Emphasizing public interfaces during refactoring protects implementation details from being locked into tests. By validating behavior through integration-style tests rather than internal code, test-driven development enables safer refactoring and progressive disclosure of design guidance without breaking existing functionality.

Can I use TDD for planning and early validation before writing implementation code?

Yes, TDD supports planning and early validation through red-green-refactor cycles. By defining tests against public interfaces first, you establish clear requirements and software design constraints before committing to implementation, using tracer bullets to validate vertical slices incrementally.