tdd

Enforce the RED/GREEN/REFACTOR cycle for test-first development.

1|Updated Mar 29, 2026

Search Tags:#testing #tdd #red-green-refactor #software-engineering #development-process

Ready to run

npx skills add https://github.com/Olino3/anvil --skill tdd-olino3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Olino3/anvil/tree/main/plugins/anvil/skills/tdd
Command: npx skills add https://github.com/Olino3/anvil --skill tdd-olino3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD discipline reference provides a language-agnostic blueprint for enforcing a structured, test-first approach within Anvil's agent-driven workflow.

Core Features & Use Cases

RED — Write a failing test that specifies the desired behavior.
GREEN — Implement the minimal production code needed to pass the test.
REFACTOR — Clean up code while preserving behavior and test results.
Use Case — Integrate the cycle into ticket workflows so each feature yields two commits (tests and implementation) and maintains test coverage.

Quick Start

Trigger the RED/GREEN/REFACTOR cycle for a new feature by writing a failing test, implementing the minimal code to pass it, and refactoring.

Frequently Asked Questions about tdd

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

FAQPage Schema

How do I enforce test-first development across an automated agent workflow?▼

To enforce test-first development, this Skill coordinates the RED/GREEN/REFACTOR cycle within the Anvil dev-agent workflow. It drives feature development by requiring explicit, reproducible steps: writing a failing test, implementing minimal code to pass, and refactoring while preserving behavior.

What is the RED/GREEN/REFACTOR cycle and how does it drive feature development?▼

The RED/GREEN/REFACTOR cycle is a test-first development process where RED writes a failing test specifying desired behavior, GREEN implements minimal production code to pass, and REFACTOR cleans up code while preserving test results. This cycle drives disciplined feature development.

Can I use this TDD process with any programming language and project setup?▼

Yes, this TDD process works across any programming language and project setup. It provides a language-agnostic blueprint that coordinates test-first cycles within the Anvil dev-agent workflow without requiring specific frameworks or dependencies.

How do I integrate the test-driven development cycle into ticket workflows?▼

You integrate the test-driven development cycle into ticket workflows by triggering the RED/GREEN/REFACTOR steps for each feature. This yields two commits per feature—one for tests and one for implementation—maintaining test coverage and ensuring commit hygiene.

Does this test-first approach require specific dependencies or components to run?▼

No, this test-first approach requires no specific dependencies or components. It functions as a discipline reference and blueprint that aligns with metadata-driven discovery to enforce the TDD process across any existing project environment.

When should I not use a strict test-driven development cycle for feature development?▼

You should not use a strict test-driven development cycle when a feature requires exploratory prototyping without defined behavior specifications. The cycle mandates explicit, reproducible steps starting with a failing test, which suits structured feature development over open-ended experimentation.