tdd

Guide test-driven development with red-green-refactor cycles and one-test-at-a-time steps.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/fray-cloud/coin --skill tdd-fray-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/fray-cloud/coin/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/fray-cloud/coin --skill tdd-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams adopt test-driven development to reduce bugs, improve design, and make refactors safer by guiding developers through the red-green-refactor loop.

Core Features & Use Cases

  • Vertical slices: drive implementation end-to-end from failing test to passing code with public interfaces.
  • Tracer bullets: plan minimal changes as one-test-at-a-time steps before coding.
  • Integration and refactor guidance: emphasize testability and safe incremental improvements across frontend and backend tasks.

Quick Start

Write a failing test for a new feature, then implement only enough code to make it pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
How does test-driven development improve software quality during refactoring?

Test-driven development reduces bugs by enforcing red-green-refactor cycles, ensuring every code change is verified by a failing test first. This structured workflow produces reliable integration tests and safer incremental refactors across frontend and backend tasks.

What's the best way to start building vertical slices using test-first development?

To build vertical slices using test-first development, write a failing test for a new feature, then implement only enough code to make it pass. This drives implementation end-to-end from failing test to passing code using explicit public interfaces.

How do tracer bullets help plan minimal changes for one-test-at-a-time cycles?

Tracer bullets help plan minimal changes by mapping out one-test-at-a-time steps before coding begins. This approach structures the test-driven development workflow, supporting testability and incremental refactoring across the software project.

Can I use test-driven development for both frontend and backend integration testing?

Yes, you can use test-driven development for both frontend and backend integration testing. The workflow emphasizes testability and safe incremental improvements, applying structured red-green-refactor cycles across all software project tasks.

When should I not use red-green-refactor cycles for feature implementation?

You should avoid red-green-refactor cycles when a software project lacks explicit interfaces or cannot support incremental refactoring. The workflow requires testability and one-test-at-a-time steps to effectively drive implementation from failing tests to passing code.