tdd

Enforce test-first development using the RED-GREEN-REFACTOR workflow.

24|5|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Luohaothu/everything-codex --skill tdd-luohaothu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Luohaothu/everything-codex/tree/main/skills/tdd
Command: npx skills add https://github.com/Luohaothu/everything-codex --skill tdd-luohaothu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development enforces writing tests before code to improve reliability, catch regressions early, and guide design.

Core Features & Use Cases

  • Enforces RED-GREEN-REFACTOR cycle for every feature or bug fix
  • Guides teams to achieve and document minimum test coverage
  • Supports planning, implementation, and refactoring workflows across projects

Quick Start

Follow the RED-GREEN-REFACTOR process to implement a feature by first writing failing tests, then code, and finally refactor

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I implement test-driven development for new software features?▼

Test-driven development is implemented by following the RED-GREEN-REFACTOR cycle: write a failing unit test, write code to pass it, then refactor. This enforces test-first development to guide design and catch regressions early.

What is the RED-GREEN-REFACTOR workflow in testing?▼

The RED-GREEN-REFACTOR workflow is a test-first process where you write a failing test, implement the minimum code to make it pass, and then clean up the code. It guides teams through feature implementation and refactoring.

How do I enforce minimum test coverage during refactoring?▼

To enforce minimum test coverage during refactoring, apply test-first development rules that require 80% or higher coverage and demand clearly documented test outcomes across all software project workflows.

Can I use test-first development for both bug fixes and new features?▼

Yes, test-first development applies to new features, bug fixes, and refactoring tasks across software projects. It enforces the RED-GREEN-REFACTOR cycle to improve code quality and reliability in all scenarios.

Why write unit tests before implementation code?▼

Writing unit tests before implementation improves reliability by catching regressions early and guiding code design. This test-first approach ensures the RED-GREEN-REFACTOR workflow shapes a robust, testable architecture.

What is the best way to integrate unit tests and integration tests using TDD?▼

The best way to integrate tests using TDD is strictly following the RED-GREEN-REFACTOR cycle for all test types. This ensures 80%+ test coverage and clearly documented outcomes to validate integration behavior and code quality.