tdd-protocol

Enforce red-green-refactor TDD cycles across multi-agent coding environments.

9|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill tdd-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-protocol
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/tdd-protocol
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill tdd-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforces the red-green-refactor TDD discipline so that no production code is written without a failing test.

Core Features & Use Cases

  • Ensures deterministic red-green-refactor cycles during code changes across multi-agent environments.
  • Captures evidence via post-test logs and commit history to prove discipline.
  • Provides foundational guidance and references to sustain TDD practices across teams.

Quick Start

Execute a code change by writing a failing test first, verify it fails, implement the minimal code to pass, then commit the green state.

Frequently Asked Questions about tdd-protocol

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

FAQPage Schema
How do I enforce strict TDD discipline across multi-agent coding environments?

Strict TDD discipline is enforced by guiding engineers through RED/GREEN/REFACTOR/COMMIT steps for each feature, ensuring no production code is written without a failing test first.

What is the red-green-refactor cycle and how do I apply it during code changes?

The red-green-refactor cycle requires writing a failing test first, implementing the minimal code to pass that test, then refactoring while maintaining the green state before committing.

Can I use this TDD protocol with Claude Code, OpenAI Codex, and Google Antigravity?

Yes, this TDD protocol applies across Claude Code, OpenAI Codex, and Google Antigravity contexts, guiding engineers through consistent red-green-refactor-commit cycles in each environment.

How do I verify TDD cycles and maintain an audit trail for code quality?

TDD cycles and audit trails are verified using a post-test log hook that captures evidence via post-test logs and commit history to prove discipline was maintained.

Do I need a specific SKILL.md format to implement this testing discipline?

Yes, you need a YAML frontmatter with name and description fields in SKILL.md, along with optional references, scripts, and assets directories to sustain the TDD practice.

What's the best way to prevent writing production code without a failing test?

The best way to prevent untested production code is enforcing deterministic red-green-refactor cycles that require a failing test to exist before any implementation code is written.