tdd-execution

Coordinate tester and coder agents to run RED-GREEN TDD phases per story.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/metasaver/claude-marketplace --skill tdd-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-execution
Source: https://github.com/metasaver/claude-marketplace/tree/main/plugins/metasaver-core/skills/workflow-steps/tdd-execution
Command: npx skills add https://github.com/metasaver/claude-marketplace --skill tdd-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill drives a test-first development flow by spawning tester and coder agents to produce tests and implement code.

Core Features & Use Cases

  • Per-story TDD: RED phase writes tests, GREEN phase implements to pass tests.
  • Wave orchestration: Parallelizable waves with sequential RED→GREEN per story.
  • Audit-ready traces: Updates stories with test and implementation metadata.

Quick Start

Start TDD execution for each story in the current wave to generate tests and implementations.

Frequently Asked Questions about tdd-execution

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

FAQPage Schema
How do I execute test-driven development with automated test and code generation?

Test-driven development execution automates the RED-GREEN cycle by spawning tester agents to write tests first, then coder agents to implement code that passes those tests. This Skill coordinates that workflow across user stories with acceptance criteria, enabling parallel processing of up to 10 concurrent tester-coder pairs while maintaining sequential RED→GREEN phases within each story.

Can I run TDD in parallel across multiple user stories?

Yes. This Skill organizes work into waves where each wave contains multiple user stories. Within each story, RED and GREEN phases run sequentially, but across different stories in the same wave, tester-coder pairs execute in parallel—up to 10 concurrent pairs—for faster delivery.

What input do I need to start TDD execution?

User stories must include acceptance criteria and an execution plan structured as waves. The Skill then spawns agents to generate tests and implementations, tracks status through metadata updates, and verifies all tests pass before marking completion.

How does agent orchestration improve test-first workflows?

Agent orchestration automates role separation: dedicated tester agents write comprehensive tests during the RED phase, while dedicated coder agents implement features to pass those tests during GREEN. This reduces context switching and ensures tests genuinely drive design before code is written.

What happens after tests and code are generated?

The Skill updates user stories with test and implementation metadata for audit trails, verifies all tests pass against the generated code, and marks the story complete only after both phases succeed—providing visibility into what was tested and implemented.

Does this work for large-scale feature delivery?

Yes. Wave-based orchestration scales across multiple concurrent tester-coder pairs (up to 10), making it suitable for delivering multiple user stories in parallel while maintaining test-first discipline and sequential RED→GREEN integrity per story.