tdd

Guide red-green-refactor cycles for test-driven feature development.

5|1|Updated Feb 11, 2026

Search Tags:#tdd #qa #red-green-refactor #integration-testing #test-driven-development #vertical-slice #software-testing

Ready to run

npx skills add https://github.com/Tristan578/project-forge --skill tdd-tristan578

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Tristan578/project-forge/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/Tristan578/project-forge --skill tdd-tristan578

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD promotes designing with testable interfaces and reduces regressions by guiding users to write tests first; this skill provides a structured approach to applying red-green-refactor cycles, ensuring features are implemented to meet public behavior expectations.

Core Features & Use Cases

Red-Green-Refactor loop: structure for rapid, iterative development cycles driven by tests.
Integration-style testing guidance: emphasizes end-to-end validation through public APIs.
Vertical-slice planning: encourages focused, one-feature-at-a-time progress from spec to code.

Quick Start

Request feature development using TDD, and I will guide you through the red-green-refactor cycle to implement it.

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 the red-green-refactor cycle work?▼

Test-driven development means writing tests before implementing features. The red-green-refactor cycle starts with a failing test, writes code to make it pass, then refactors while keeping tests green to reduce regressions.

How do I write integration tests before implementing a new feature?▼

Form your public interfaces through integration tests first. This validates end-to-end behavior through public APIs before writing implementation code, ensuring features meet expected external behaviors.

Can I use test-driven development to fix bugs in existing software projects?▼

Yes, test-driven development is useful when fixing bugs in software projects. You write a failing test that reproduces the bug, then implement the fix to make the test pass and prevent future regressions.

What is vertical-slice planning in test-driven development?▼

Vertical-slice planning in test-driven development encourages focused, one-feature-at-a-time progress from specification to code. It structures rapid, iterative development cycles driven by tests for each slice.

When should I not use test-driven development for software testing?▼

Test-driven development may be less suitable for exploratory software testing or throwaway prototypes where public behavior expectations are undefined. It requires having clear feature specifications to form testable interfaces beforehand.