tdd-orchestration
TDD Orchestration Skill
Master TDD orchestrator ensuring strict red-green-refactor discipline with multi-agent coordination, a Layer-0 domain-modeling gate, and principled DRY enforcement at Refactor. Dual-mode: Claude Teams (preferred) for parallel work with plan approval, or sequential subagent delegation (fallback).
Description
Orchestrates Test-Driven Development workflows sharpened by two lenses that never displace red-green-refactor — they gate it at plan review:
- DDD at Layer 0 blocks Red until a Domain Model Plan is approved (concepts named in business vocabulary, entity vs. value object decided, primitive obsession audited, domain/infrastructure boundary drawn, test-name shapes using ubiquitous language).
- DRY at Refactor rejects extractions of ≤2 occurrences or of accidentally-similar syntax; deduplication is reserved for same-concept repetition at ≥3 sites.
Discipline Layering (the task board)
Layer 0: Domain Model — specialist plans concepts, types, boundaries; BLOCKS all Red
Layer 1: Red — test-writer writes failing tests using domain vocabulary
Layer 2: Green — implementer passes tests; domain types preserved
Layer 3: Refactor — DRY discipline; promote primitives to value objects
Layer 4: Quality — review
Layer 5: Integration — integration tests
Layer 6: Synthesis — final report
The orchestrator enforces both lenses at plan review — implementers apply them, the orchestrator validates them.
What's Included
- Examples: Multi-agent TDD workflows with the Layer 0 gate, team-mode orchestration, Domain Model Plan samples
- Reference: TDD best practices, red-green-refactor patterns, coverage strategies, DDD building blocks
- Templates: Task board templates (Layers 0–6), test planning structures, Domain Model Plan template
- Checklists: Domain Model plan approval, Red/Green/Refactor review, DRY discipline, coverage validation
Use This Skill When
- Implementing features with strict TDD methodology
- Modeling a domain before the first test (entities, value objects, aggregates)
- Coordinating multiple agents in TDD workflow
- Enforcing test-first development with ubiquitous language
- Achieving >90% test coverage
- Refactoring with principled DRY (avoiding premature abstractions)
- Orchestrating TDD teams with parallel component work
- Managing plan approval gates for TDD + DDD compliance
Related Agents
tdd-orchestrator- Multi-agent TDD coordinator (team + subagent modes, Layer-0 gate)tdd-typescript-implementer- TypeScript/JavaScript TDD with branded typestdd-python-implementer- Python TDD with Pydantic / NewType / frozen dataclassestest-generator- Automated test creationcode-quality-analyzer- Code quality review
Skill Version: 2.1
More from greyhaven-ai/claude-code-config
grey-haven-creative-writing
Professional writing assistance for blogs, research articles, fiction, essays, and marketing copy. Use when users want to write, edit, or improve any form of written content. Triggers: 'write a blog', 'write an article', 'help me write', 'write a story', 'write a chapter', 'draft an essay', 'creative writing', 'improve my writing', 'edit my writing', 'write copy', 'content writing'.
139creative-writing
Professional writing assistance for blogs, research articles, fiction, essays, and marketing copy. Use when users want to write, edit, or improve any form of written content. Triggers: 'write a blog', 'write an article', 'help me write', 'write a story', 'write a chapter', 'draft an essay', 'creative writing', 'improve my writing', 'edit my writing', 'write copy', 'content writing'.
35grey-haven-prompt-engineering
Master 26 documented prompt engineering principles for crafting effective LLM prompts with 400%+ quality improvement. Includes templates, anti-patterns, and quality checklists for technical, learning, creative, and research tasks. Use when writing prompts for LLMs, improving AI response quality, training on prompting, designing agent instructions, or when user mentions 'prompt engineering', 'better prompts', 'LLM quality', 'prompt templates', 'AI prompts', 'prompt principles', or 'prompt optimization'.
12grey-haven-ontological-documentation
Create comprehensive ontological documentation for Grey Haven systems - extract domain concepts from TanStack Start and FastAPI codebases, model semantic relationships, generate visual representations of system architecture, and document business domains. Use when onboarding, documenting architecture, or analyzing legacy systems.
12grey-haven-api-design
Design RESTful APIs following Grey Haven standards - FastAPI routes, Pydantic schemas, HTTP status codes, pagination, filtering, error responses, OpenAPI docs, and multi-tenant patterns. Use when creating API endpoints, designing REST resources, implementing server functions, configuring FastAPI, writing Pydantic schemas, setting up error handling, implementing pagination, or when user mentions 'API', 'endpoint', 'REST', 'FastAPI', 'Pydantic', 'server function', 'OpenAPI', 'pagination', 'validation', 'error handling', 'rate limiting', 'CORS', or 'authentication'.
12grey-haven-smart-debugging
AI-powered intelligent debugging with stack trace analysis, error pattern recognition, and automated fix suggestions. Use when debugging complex errors, analyzing stack traces, or performing root cause analysis. Triggers: 'debug', 'error analysis', 'stack trace', 'root cause', 'troubleshooting'.
10