tdd-orchestrate

Enforce red-green-refactor TDD with role-specific subagents and verification gates.

2|1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/kelp/kelp-claude-plugins --skill tdd-orchestrate-kelp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-orchestrate
Source: https://github.com/kelp/kelp-claude-plugins/tree/main/plugins/tdd-pipeline/skills/tdd-orchestrate
Command: npx skills add https://github.com/kelp/kelp-claude-plugins --skill tdd-orchestrate-kelp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents skipped tests, self-reviewed stubs, and ad-hoc edits by enforcing a disciplined red-green-refactor workflow or a full seven-agent pipeline so every change is verified, reviewed, and gated before integration.

Core Features & Use Cases

  • Inline red-green-refactor for quick fixes and small changes: read code, write a failing test, implement the minimal change, run the suite, refactor if needed, and commit.
  • Seven-agent pipeline for new modules or multi-behavior tasks: dispatch test-writer, test-reviewer, red gate, implementer, verify gate, code-reviewer, and integrator with strict fix loops and escalation.
  • Gates and verification: enforce compile-and-fail red gates, run CLAUDE.md test and lint commands, require reviewer approval, and update build files only after integration stage.
  • Use Cases: implement a new parser module with multiple behaviors, fix a regression with clear test coverage, or onboard TDD enforcement in an existing project.

Quick Start

Ask the orchestrator to run TDD for your task in one sentence, for example: /tdd-orchestrate implement the parser module with tokenization, error handling, and serialization.

Frequently Asked Questions about tdd-orchestrate

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

FAQPage Schema
How do I enforce strict red-green-refactor test-driven development for code changes?

Enforce strict red-green-refactor test-driven development by applying inline cycles for small changes or dispatching a seven-agent pipeline for modules with three or more behaviors. Compile-and-fail red gates, test execution, and lint checks validate every change before integration.

What is the seven-agent TDD pipeline and when do I need it?

The seven-agent TDD pipeline dispatches test-writer, test-reviewer, red gate, implementer, verify gate, code-reviewer, and integrator subagents to enforce strict fix loops and escalation. Use this pipeline when implementing new modules or tasks involving three or more behaviors.

How do I run a TDD workflow for a new parser module with multiple behaviors?

Run a TDD workflow for a new parser module by dispatching the seven-agent pipeline, which separates test writing, implementation, and code review into gated stages. Subagents enforce compile-and-fail red gates and require reviewer approval before updating build files.

Can I use inline red-green-refactor cycles for fixing small bugs and regressions?

Yes, you can use inline red-green-refactor cycles for fixing small bugs and regressions. The orchestrator defaults to inline cycles for small changes, allowing you to read code, write a failing test, implement the minimal change, run the test suite, and commit without dispatching the full pipeline.

How does the TDD pipeline handle repeated code review rejections?

The TDD pipeline handles repeated code review rejections by enforcing strict reviewer fix-loops and escalating after repeated rejections. The code-reviewer subagent gates the process until issues are resolved, preventing self-reviewed stubs and ad-hoc edits from integrating.