tdd

Orchestrate red-green-refactor cycles with test-first practices and public API validation.

20|6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/adrielp/ai-engineering-harness --skill tdd-adrielp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/adrielp/ai-engineering-harness/tree/main/gemini/skills/tdd
Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill tdd-adrielp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development guidance helps teams build features by writing tests first, ensuring clearer requirements and safer refactors.

Core Features & Use Cases

  • Red-Green-Refactor workflow guidance for incremental development
  • Integration-style tests that validate public interfaces and real behavior
  • Clear examples and anti-patterns to avoid brittle tests and overfitting

Quick Start

Begin by writing one failing test for a small feature, then implement only enough code to pass it.

Frequently Asked Questions about tdd

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

FAQPage Schema
What is the red-green-refactor cycle in test-driven development?

The red-green-refactor cycle in test-driven development is a workflow where you first write a failing test, implement the minimum code to make it pass, and then safely refactor the implementation without changing its external behavior.

How do I start writing integration tests using a test-first approach?

To start writing integration tests using a test-first approach, begin by writing one failing test that validates a small feature through its public API, then implement only enough code to pass that test before moving on to the next cycle.

Can I use test-driven development workflows for large codebases?

Yes, you can use test-driven development workflows for large codebases. This approach orchestrates TDD cycles and integration-style testing to deliver features with confidence across small to large software projects that require ongoing refactoring.

Why do my test-driven development tests become brittle and overfit?

Test-driven development tests become brittle and overfit when they validate internal implementation details rather than public interfaces. You can avoid this by using integration-style tests that validate real behavior through public APIs instead.

When should I not use test-driven development for a software project?

You should not use test-driven development when your software project lacks clear requirements or public APIs to validate against, as the workflow relies on writing tests first to enforce incremental development and safer refactoring.