tdd

Guide TDD workflows with failing-test-first and red-green-refactor cycles.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/ddsyasas/pomodoro-app-shared --skill tdd-ddsyasas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/ddsyasas/pomodoro-app-shared/tree/main/pomodoro-app/.claude/skills/tdd
Command: npx skills add https://github.com/ddsyasas/pomodoro-app-shared --skill tdd-ddsyasas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD provides a guided, test-first workflow to help teams implement features with fewer bugs and clearer requirements.

Core Features & Use Cases

  • Structured RED-GREEN-REFACTOR cycles for feature development, bug fixes, and new use cases
  • Protocols for writing failing tests first, minimal production code, and disciplined refactoring
  • Use case: when designing handlers, services, or use cases, this skill ensures changes are well-tested and maintainable

Quick Start

Begin a TDD cycle by writing a failing test for the next increment, then implement just enough production code to make it pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
What is the test-driven development workflow for implementing new features?

The test-driven development workflow applies Uncle Bob's Three Laws to guide feature implementation through structured RED-GREEN-REFACTOR cycles, enforcing failing-test-first discipline to maintain clean, testable code.

How do I start a red-green-refactor cycle when fixing bugs?

Begin a red-green-refactor cycle by writing a failing test for the next increment, then implement minimal production code to pass it, and refactor the code to maintain clean, testable standards.

Can I use test-driven development for building handlers and services?

Yes, test-driven development applies to designing handlers, services, or use cases by enforcing a test-first workflow that ensures software engineering changes are well-tested and maintainable.

Why does test-driven development require writing a failing test first?

Test-driven development requires a failing test first because Uncle Bob's Three Laws mandate writing test code before production code to clarify requirements and guide minimal software engineering implementation.

What's the best way to maintain clean code during test-driven development?

Maintain clean code during test-driven development through disciplined refactoring within the RED-GREEN-REFACTOR cycle, ensuring minimal production code passes tests while keeping software engineering standards high.

Do I need unit-testing frameworks to follow test-driven development?

Unit-testing frameworks are required to execute failing tests first and validate minimal production code during the red-green-refactor cycles that test-driven development enforces for software engineering.