Coordinate four-stage TDD workflows with specialized subagents.
npx skills add https://github.com/patrob/skills --skill tdd-cycle-patrob
Please help me install this Agent Skill. Skill: tdd-cycle Source: https://github.com/patrob/skills/tree/main/plugins/claude-skills/skills/tdd-cycle Command: npx skills add https://github.com/patrob/skills --skill tdd-cycle-patrob
Coordinating a four-stage TDD workflow to drive a single success criterion to green using specialized subagents. The orchestration runs inside each workstream under /orchestrate, cycling through Test Writer, Implementer, Verifier, and Fix Loop stages. The workflow enforces a strict delegation contract and never edits production code or tests.
Run the tdd-cycle workflow on a single criterion to orchestrate the four-stage pipeline automatically.
High-intent search queries and answers about installing and using this skill.
You coordinate a TDD workflow with multiple agents by running a four-stage pipeline using specialized subagents for test writing, implementation, verification, and fixing. The orchestrator enforces a strict delegation contract, cycling through each stage until the success criterion turns green.
Automating test-driven development for a single criterion is best handled by orchestrating dedicated subagents that write tests, implement code, and verify results. This workflow operates under /orchestrate and produces a final CYCLE_REPORT with implementation and verification outcomes.
The delegation contract in a multi-agent TDD pipeline ensures the coordinator never edits production code or tests directly. It relies entirely on specialized subagents—the Test Writer, Implementer, Verifier, and Fix Loop—to execute changes and report back results.
Yes, you can use this TDD cycle workflow inside an existing orchestration workstream. The orchestration runs inside each workstream under /orchestrate, driving a single success criterion to green through its four specialized subagent stages.
A limitation of using this TDD coordinator is that it operates strictly on a single success criterion per cycle and never edits production code or tests itself. All code modifications are strictly delegated to the four subagent stages, requiring clear criterion definition beforehand.
patrobLaunch parallel workstreams in isolated git worktrees with TDD cycles.
sQVeClose br epics after evidence-backed checks pass and append an Outcome.
VanLAnalyze Git commit history to generate engineering retrospectives with team activity and code quality metrics.
darthlinuxerGuide software development through the RED-GREEN-REFACTOR test-first cycle.
