tdd

Implement features using red-green-refactor test-driven development workflows.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/bartolomeomueller/hr --skill tdd-bartolomeomueller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/bartolomeomueller/hr/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/bartolomeomueller/hr --skill tdd-bartolomeomueller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) helps teams build features with confidence by validating desired behavior through tests before implementing code, reducing regressions and refactors.

Core Features & Use Cases

  • End-to-end verification via small, observable behaviors that reflect public interfaces.
  • Iterative red-green-refactor workflow that minimizes work in progress and keeps code clean.
  • Tests guiding API design and maintaining long-term software quality across feature work.

Quick Start

Write one end-to-end test that captures a single observable behavior, then implement only the minimum 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 test-driven development and how does it accelerate feature delivery?

Test-driven development is a test-first workflow that validates desired behavior through tests before implementing code. This iterative red-green-refactor cycle reduces regressions and keeps code clean, ultimately accelerating feature delivery by minimizing work in progress.

How do I start writing tests using the red-green-refactor workflow?

To start red-green-refactor, write one end-to-end test capturing a single observable behavior, then implement only the minimum code required to make it pass. This iterative workflow enforces vertical slicing and incremental behavioral validations across feature campaigns.

Does test-driven development work for integration testing and API design?

Test-driven development works effectively for integration testing and API design by enforcing public-interface testing. Tests guide API design by validating small, observable behaviors that reflect public interfaces, maintaining long-term software quality across feature work.

When should I use test-first development instead of writing tests after implementation?

Use test-first development when building features that require robust test suites and behavioral validations. It minimizes regressions during iterative refactors and ensures software projects maintain confidence in desired behavior through end-to-end verification before code implementation.

What are the limitations of applying test-driven development to software projects?

Test-driven development requires discipline to enforce public-interface testing and vertical slicing. It may slow initial feature delivery due to writing tests first, but minimizes regressions and refactors long-term by validating explicit behavioral validations incrementally.