test-driven-development

Guide RED/GREEN cycles and behavioral test construction for TDD workflows.

Updated Apr 24, 2026

Search Tags:#automation #workflow #testing #tdd #orchestration #red-green

Ready to run

npx skills add https://github.com/michael-conrad/.opencode --skill test-driven-development-michael-conrad

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/michael-conrad/.opencode --skill test-driven-development-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing tests before implementation is error-prone and inconsistent; this skill provides structure and governance to ensure RED/GREEN cycles and behavioral test creation are consistently followed.

Core Features & Use Cases

Structured TDD orchestration across RED, GREEN, and REFACTOR phases
Behavioral-test guidance and regression-pattern generation
Safe, isolated sub-agent routing with phase gates and provenance metadata
Applicable to single-repo multi-skill environments to coordinate cross-team workflows

Quick Start

Invoke the skill to drive the RED-GREEN cycle by writing tests first and then implementing behavior.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema

How do I enforce strict test-driven development workflows across my team?▼

You can enforce strict test-driven development workflows by using structured orchestration to guide RED, GREEN, and REFACTOR cycles, ensuring tests are consistently written before implementation. This provides behavioral test governance and phase gates.

What is the best way to structure behavioral tests and regression patterns?▼

Structuring behavioral tests and regression patterns is best handled by guiding the RED/GREEN cycle to write tests first, then generating regression patterns during the refactor phase with provenance metadata for compliance.

How do I start a RED-GREEN cycle for writing tests before implementation?▼

To start a RED-GREEN cycle, invoke the orchestration skill to drive the process by writing red tests first and then implementing the green behavior, applying structured task discipline and safe sub-agent routing.

Can I use TDD orchestration within a single-repo multi-skill environment?▼

Yes, TDD orchestration is applicable to single-repo multi-skill environments to coordinate cross-team workflows, utilizing a Trigger Dispatch Table interface and phase gates to ensure safe, isolated sub-agent routing.

Why does writing tests before implementation become inconsistent without governance?▼

Writing tests before implementation becomes inconsistent without governance because the process is error-prone, lacking the structured task discipline, phase gates, and compliance metadata needed to enforce proper RED/GREEN cycles.