playbooks

home / skills / greyhaven-ai / claude-code-config / tdd-orchestration

tdd-orchestration skill

/grey-haven-plugins/core/skills/tdd-orchestration

This skill orchestrates multi-agent TDD workflows with strict red-green-refactor, automated test generation, and 90+ percent coverage gates.

npx playbooks add skill greyhaven-ai/claude-code-config --skill tdd-orchestration

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
2.8 KB
---
name: grey-haven-tdd-orchestration
description: "Master TDD orchestration with multi-agent coordination, strict red-green-refactor enforcement, automated test generation, coverage tracking, and >90% coverage quality gates. Supports Claude Teams for parallel TDD workflows with plan approval gates, or falls back to sequential subagent coordination. Coordinates tdd-python, tdd-typescript, and test-generator agents. Use when implementing features with TDD workflow, coordinating multiple TDD agents, enforcing test-first development, orchestrating TDD teams, or when user mentions 'TDD workflow', 'test-first', 'TDD orchestration', 'multi-agent TDD', 'test coverage', or 'red-green-refactor'."
# v2.0.43: Skills to auto-load for subagents (TDD language specialists)
skills:
  - grey-haven-tdd-typescript
  - grey-haven-tdd-python
  - grey-haven-test-generation
  - grey-haven-code-quality-analysis
# v2.0.74: Orchestrator needs full tool access for coordination
# v2.1.0: Added team tools for Claude Teams support
allowed-tools:
  - Read
  - Write
  - MultiEdit
  - Bash
  - Grep
  - Glob
  - Task
  - TodoWrite
  - Teammate
  - SendMessage
  - TaskCreate
  - TaskUpdate
  - TaskList
  - TaskGet
---

# TDD Orchestration Skill

Master TDD orchestrator ensuring strict red-green-refactor discipline with multi-agent coordination and comprehensive metrics. Supports dual-mode operation: Claude Teams (preferred) with parallel task execution and plan approval, or sequential subagent delegation (fallback).

## Description

Orchestrates Test-Driven Development workflows with automated test generation, implementation coordination, coverage tracking, and quality gates. In team mode, spawns specialist teammates (test-writer, implementer, quality reviewer) with file ownership boundaries and layered task dependencies for parallel TDD execution.

## What's Included

- **Examples**: Multi-agent TDD workflows, feature implementation with TDD, team-mode orchestration
- **Reference**: TDD best practices, red-green-refactor patterns, coverage strategies
- **Templates**: TDD workflow templates, test planning structures, team task boards
- **Checklists**: TDD verification, coverage validation, plan approval criteria

## Use This Skill When

- Implementing features with strict TDD methodology
- Coordinating multiple agents in TDD workflow
- Enforcing test-first development
- Achieving >90% test coverage
- Orchestrating TDD teams with parallel component work
- Managing plan approval gates for TDD compliance

## Related Agents

- `tdd-orchestrator` - Multi-agent TDD coordinator (team + subagent modes)
- `tdd-typescript-implementer` - TypeScript/JavaScript TDD
- `tdd-python-implementer` - Python TDD
- `test-generator` - Automated test creation
- `code-quality-analyzer` - Code quality review

---

**Skill Version**: 2.0

Overview

This skill orchestrates strict Test-Driven Development (TDD) workflows with multi-agent coordination, enforcing red-green-refactor discipline and automated quality gates. It supports parallel team-mode using Claude Teams or a sequential subagent fallback, and focuses on automated test generation plus continuous coverage tracking. The goal is reliable test-first delivery with a target of >90% coverage enforced by configurable gates.

How this skill works

The orchestrator spawns or coordinates specialized agents (test-writer, implementer, quality reviewer) and assigns file ownership and task dependencies so teams can work in parallel. It drives an explicit TDD loop: generate failing tests, implement code to make tests pass, and trigger refactor passes while automatically measuring coverage. Plan approval gates and coverage quality gates ensure each iteration meets TDD and coverage requirements before merging.

When to use it

  • Implementing new features with strict test-first discipline
  • Coordinating multiple TDD agents or specialist roles
  • Enforcing red-green-refactor workflows across a team
  • Maintaining or achieving >90% test coverage with automated gates
  • Orchestrating plan approval gates or team-mode parallel work

Best practices

  • Define clear file ownership and granular task boundaries for parallel work
  • Keep test cases small and focused; ensure tests fail before implementing
  • Use plan approval gates to review test intent before implementation
  • Automate coverage checks and fail CI on regression below thresholds
  • Run short refactor passes with dedicated reviews to preserve behavior

Example use cases

  • Spin up a Claude Teams workflow: test-writer, implementer, reviewer run in parallel on a feature branch with a plan approval gate
  • Fallback to sequential subagent mode for single-agent environments or limited concurrency
  • Generate tests automatically for a new API endpoint, then coordinate TypeScript and Python implementers to satisfy them
  • Enforce a >90% coverage gate in CI so merges require passing tests and coverage thresholds
  • Orchestrate cross-language features where tdd-python and tdd-typescript agents implement language-specific modules

FAQ

What happens if Claude Teams is not available?

The orchestrator falls back to sequential subagent coordination, preserving the TDD loop but executing tasks one after another instead of in parallel.

How are coverage thresholds enforced?

Coverage is measured automatically each iteration and quality gates block merges or advances if the configured threshold (default >90%) is not met.