test-driven-development

Enforce test-first development through the Red-Green-Refactor cycle.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill test-driven-development-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/test-driven-development
Command: npx skills add https://github.com/yckkkk/reo --skill test-driven-development-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing code without tests leads to undetected regressions and unclear behavior. This skill promotes a test-first approach to ensure changes are driven by failing tests and validated by reliable outcomes.

Core Features & Use Cases

  • Enforces Red-Green-Refactor workflow to ensure tests guide implementation.
  • Applies to new features, bug fixes, and refactors to prevent regressions.
  • Improves confidence and maintainability by validating test-driven discipline across codebases.

Quick Start

Create a failing test for the intended feature, then write the minimal production code to satisfy the test.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I start test-driven development for a new feature?

To start test-driven development, create a failing test for the intended feature, then write the minimal production code required to satisfy that test before refactoring safely.

What is the Red-Green-Refactor cycle in unit testing?

The Red-Green-Refactor cycle is a test-driven development workflow where you write a failing test (red), implement minimal code to pass it (green), and then safely improve the code (refactor).

Does test-first development work for bug fixes and refactoring?

Yes, test-first development applies to bug fixes and refactoring by ensuring explicit failing tests precede code changes, preventing regressions across typical software projects.

Why does writing code without tests cause regressions?

Writing code without tests causes undetected regressions and unclear behavior because changes lack validation, whereas a test-first approach ensures changes are driven by failing tests and validated by reliable outcomes.

What's the best way to enforce disciplined unit testing practices?

The best way to enforce disciplined unit testing practices is to adopt a test-first development skill that mandates a failing test precedes production code across features, bug fixes, and refactors.