Agent skill
cobuilder:tdd-pipeline
This skill should be used when System 3 or Guardian needs to "generate a TDD pipeline", "create a worker pipeline", "instantiate the tdd-validated template", "set up TDD execution pipeline", or when creating DOT pipeline files for test-driven worker execution. Documents the tdd-validated template and worker powers configuration.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tdd-pipeline
SKILL.md
TDD Pipeline Template
The tdd-validated template generates DOT pipeline files with explicit RED → GREEN → REFACTOR nodes per worker. Each worker receives superpowers for TDD, debugging, and verification.
Template Location
.cobuilder/templates/tdd-validated/
Instantiation
python3 cobuilder/templates/instantiator.py tdd-validated \
--param prd_ref=PRD-AUTH-001 \
--param sd_path=docs/sds/SD-AUTH-001.md \
--param-file workers.yaml \
--output .pipelines/pipelines/auth-tdd.dot
Workers YAML Format
workers:
- label: "User Login"
worker_type: backend-solutions-engineer
bead_id: AUTH-LOGIN
acceptance: "Login endpoint returns JWT token for valid credentials"
scope: "src/auth/login.py,tests/test_login.py"
test_command: "pytest tests/test_login.py -v"
- label: "Login Form"
worker_type: frontend-dev-expert
bead_id: AUTH-FORM
acceptance: "Login form submits credentials and stores JWT"
scope: "src/components/LoginForm.tsx,tests/LoginForm.test.tsx"
test_command: "npm test -- --testPathPattern=LoginForm"
Pipeline Structure Per Worker
Each worker gets three codergen nodes in sequence:
RED (write failing tests) → GREEN (minimal implementation) → REFACTOR (clean up)
→ Validation Gate → Decision (pass → next | fail → retry from RED)
Color coding: RED nodes = #ffcccc, GREEN nodes = #ccffcc, REFACTOR nodes = #ccccff
Worker Powers Configuration
All codergen nodes in the TDD template receive worker_powers attribute:
| Power Key | Sub-Skills Available | Default |
|---|---|---|
tdd |
cobuilder:tdd, cobuilder:verification-before-completion |
Yes |
systematic-debugging |
cobuilder:systematic-debugging |
Yes |
verification |
cobuilder:verification-before-completion |
Yes |
brainstorming |
cobuilder:brainstorming |
No |
all |
All cobuilder sub-skills | No |
Default: tdd,systematic-debugging,verification
Override per-worker:
workers:
- label: "Complex UI"
worker_powers: "all" # Full power mode for complex tasks
Template Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
prd_ref |
Yes | — | PRD identifier |
sd_path |
Yes | — | Path to Solution Design |
workers |
Yes | — | List of worker definitions |
include_research |
No | false |
Prepend research node |
include_e2e |
No | true |
Append E2E integration test node |
default_worker_powers |
No | tdd,systematic-debugging,verification |
Power set for all workers |
llm_profile_test |
No | anthropic-fast |
LLM for RED phase (test writing) |
llm_profile_impl |
No | anthropic-smart |
LLM for GREEN phase (implementation) |
llm_profile_refactor |
No | anthropic-fast |
LLM for REFACTOR phase |
Validation
After generating a pipeline, validate it:
python3 cobuilder/engine/cli.py validate .pipelines/pipelines/auth-tdd.dot
Then launch:
python3 cobuilder/engine/pipeline_runner.py --dot-file .pipelines/pipelines/auth-tdd.dot
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?