tdd

Enforce test-driven development with red-green-refactor cycles and integration-style validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development reduces defect rates by ensuring that software behavior is defined by tests before implementation, aligning teams around verifiable outcomes and protecting against brittle refactors.

Core Features & Use Cases

  • Structured workflow: Planning, tracer bullets, vertical slicing, and red-green-refactor cycles guide feature delivery and bug fixes with measurable progress.
  • Guardrails and best practices: Emphasizes testing through public interfaces, avoids testing internal details, and promotes end-to-end integration-style checks.
  • Real-world use case: When starting a new feature, write a single end-to-end test for the desired behavior, then implement the minimal code to pass it, iterating until all scenarios are covered.

Quick Start

Begin a tracer bullet by writing one end-to-end test for a desired behavior, then implement the minimal 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 start test-driven development for a new feature?

Start test-driven development by writing a single end-to-end integration test for the desired behavior, then implement the minimal code to pass it. Iterate using the red-green-refactor cycle until all scenarios are covered.

What is the red-green-refactor loop in test-driven development?

The red-green-refactor loop in test-driven development is an incremental cycle where you write a failing test, implement minimal code to pass it, then refactor while ensuring tests stay green. It guides feature delivery with measurable progress.

When should I use tracer bullets and vertical slices in TDD?

Use tracer bullets and vertical slices in test-driven development when building new features to validate architecture end-to-end early. This approach structures delivery by writing one integration test for a desired behavior before expanding implementation.

Should I test internal implementation details or public interfaces in TDD?

Test-driven development emphasizes testing through public interfaces and avoiding testing internal implementation details. This guardrail protects against brittle refactors by ensuring software behavior is defined by verifiable outcomes rather than internal coupling.

Can I use test-driven development for bug fixes and integration tests?

Yes, test-driven development applies to bug fixes by enforcing integration-style validation across plans, tests, and refactors. Write an end-to-end test reproducing the bug, then implement the fix to pass it within the red-green-refactor cycle.