tdd

Guide test-driven development with one-test-at-a-time cycles and minimal implementation.

12|1|Updated Feb 13, 2026

Search Tags:#workflow #planning #testing #tdd #refactoring #red-green-refactor

Ready to run

npx skills add https://github.com/helderberto/skills --skill tdd-helderberto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/helderberto/skills/tree/main/tdd
Command: npx skills add https://github.com/helderberto/skills --skill tdd-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gaps in test coverage and design drift when building features or fixing bugs are common; this skill provides a guided TDD workflow to keep tests and implementation aligned.

Core Features & Use Cases

Structured planning: helps define public interfaces and critical tests before coding
Tracer bullets: demonstrates the red-green-refactor loop in small, verifiable steps
Incremental cycles: enforces one-test-at-a-time progression with minimal code
References & best practices: links internal references on testing principles and refactoring

Quick Start

Outline the public interface for a feature, then write a single failing test and 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 writing tests using the red-green-refactor cycle?▼

To start the red-green-refactor cycle, outline the public interface for your feature, then write a single failing test and implement the minimal code required to pass it before refactoring.

How does test-driven development prevent design drift in new features?▼

Test-driven development prevents design drift by enforcing one-test-at-a-time incremental cycles, keeping your tests and implementation aligned through minimal code additions and safe refactoring.

Can I use this TDD workflow for fixing bugs as well as feature work?▼

Yes, this TDD workflow applies to both feature work and bug fixes across codebases, using structured planning and tracer bullets to verify behavior in small, incremental steps.

What's the best way to plan tests before writing implementation code?▼

The best way to plan tests is to define the public interfaces and identify critical tests before coding, using provided planning prompts to ensure your tests remain behavior-focused and maintainable.

Why should I write only one failing test at a time during development?▼

Writing one failing test at a time enforces incremental progression, ensuring you implement only the minimal code to reach green and maintain safe, verifiable refactoring steps throughout the cycle.