Help us improve
Share bugs, ideas, or general feedback.
From rtl-agent-team
Orchestrates a full RTL design pipeline from specification to verification using a 6-phase flow with phase gates. Use when starting a complete chip design.
npx claudepluginhub babyworm/rtl-agent-team --plugin rtl-agent-teamHow this skill is triggered — by the user, by Claude, or both
Slash command
/rtl-agent-team:rat-auto-design [spec-file or project-description][spec-file or project-description]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<Purpose>
references/review-checklist.mdtemplates/adr-template.mdtemplates/autopilot-state.jsontemplates/context-manifest-phase-1.jsontemplates/context-manifest-phase-2.jsontemplates/context-manifest-phase-3.jsontemplates/context-manifest-phase-4.jsontemplates/context-manifest-phase-5.jsontemplates/context-manifest-phase-6.jsontemplates/escalation-prompts.jsontemplates/lessons-learned-entry.mdtemplates/phase-summary.mdtemplates/review-report.mdGenerates design documents from spec through microarchitecture (Phase 1→3) with research, block architecture, reference model, and BFM, stopping before RTL for human review.
Orchestrates parallel SystemVerilog RTL design builds: decomposes into independent modules, spawns code-gen agents, lints, verifies components, and integrates top-level. Use /gf-build for RISC-V CPUs or similar.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
<Use_When>
<Do_Not_Use_When>
None — this is the full pipeline entry point. Setup is handled automatically.
# Parse mode
TEAM_MODE = "--no-team" not in ARGUMENTS
if TEAM_MODE:
# ═══ TEAM MODE: Skill sequences phases directly ═══
# State management
Write(".rat/state/rat-auto-design-state.json",
{ "schema_version": "3.0", "status": "running",
"current_phase": 1, "execution_mode": "team",
"phases": { "1": {"status":"pending"}, "2": {"status":"pending"},
"3": {"status":"pending"}, "4": {"status":"pending"},
"5": {"status":"pending"}, "6": {"status":"pending"} } })
# Phase 1: Research (team)
Skill(skill="rtl-agent-team:rtl-p1-research-team", args="$ARGUMENTS")
# Gate check + state update
# Phase 2: Architecture + RefC (team)
Skill(skill="rtl-agent-team:rtl-p2-arch-team", args="Phase 1 complete")
# Gate check + state update
# Phase 3: uArch + BFM (team)
Skill(skill="rtl-agent-team:rtl-p3-uarch-team", args="Phase 2 complete")
# Gate check + state update
# Phase 4: RTL Implementation (team)
Skill(skill="rtl-agent-team:rtl-p4-implement-team", args="Phase 3 complete")
# Gate check + state update
# Phase 5: Verification (team)
Skill(skill="rtl-agent-team:rtl-p5-verify-team", args="Phase 4 complete")
# Gate check + state update
# Phase 6: Design Review (no team — sequential only)
Bash("mkdir -p reviews/phase-6-review")
Task(subagent_type="rtl-agent-team:p6-review-orchestrator",
prompt="Execute Phase 6 design review. Context: Phase 5 PASS.")
# Mark completed (stop-gate.sh reads top-level "status" to allow exit)
# Write completed status BEFORE cleanup so stop hook sees it
# Portable in-place JSON edit — avoids GNU/BSD sed -i differences (macOS BSD sed requires `-i ''`).
Bash("python3 -c 'import json, pathlib; p = pathlib.Path(\".rat/state/rat-auto-design-state.json\"); d = json.loads(p.read_text()); d[\"status\"] = \"completed\"; p.write_text(json.dumps(d, indent=2))'")
# Cleanup state
Bash("rm -f .rat/state/rat-auto-design-state.json")
else:
# ═══ SEQUENTIAL MODE: Delegate to autopilot-orchestrator ═══
Task(subagent_type="rtl-agent-team:autopilot-orchestrator",
prompt="Execute full RTL autopilot pipeline. --no-team. User input: $ARGUMENTS")
Team mode uses native teams within each phase for parallel execution (Orchestrator as Teammate pattern). Each phase team skill handles its own TeamCreate/TeamDelete lifecycle with a coordinator teammate + 3-5 workers. Sequential mode delegates everything to the autopilot-orchestrator.
docs/phase-1-research/ through docs/phase-5-verify/reviews/phase-6-review/
(Phase 6 is the design review + documentation phase; its outputs live under reviews/, not docs/)rtl/*/*.sv — lint-clean, unit-tested RTL modulessim/ — testbenches, regression results, and coverage datareviews/ — per-phase review reports with final compliance verdict