rtl-p4-implement-team

name	rtl-p4-implement-team
description	Phase 4 RTL implementation with native team parallel workers for multi-module coding. Triggers: 'implement team', 'Phase 4 team', 'parallel implement'.
user-invocable	true
argument-hint	[module-list or --all]
allowed-tools	Bash, Read, Write, Edit, Task, Grep, Glob, TeamCreate, TeamDelete, Agent, SendMessage, TaskCreate, TaskList, TaskUpdate, AskUserQuestion

Execute Phase 4 RTL implementation pipeline using Claude Code native team infrastructure. The skill (main session) handles team lifecycle: TeamCreate, coordinator + worker spawning, task monitoring, and cleanup. The coordinator teammate manages the 10-wave task graph and directs workers via SendMessage.

<Use_When>

• Phase 3 μArch specs are complete and RTL coding is needed
• User says "implement team", "Phase 4 team", "parallel implement"
• Have 3+ modules that benefit from concurrent RTL coding workers
• Need maximum parallelism for multi-module RTL implementation </Use_When>

<Do_Not_Use_When>

• Phase 3 μArch specs are not complete (run rtl-p3-uarch-design first)
• Single module only (use rtl-p4-implement for simpler flow)
• Only need a single module bug fix (use rtl-p4s-bugfix)
• Need RTL + verification together from uarch (use rat-p4p5-impl-verify) </Do_Not_Use_When>

Prerequisites

Phase 3 completion required:

• At least one μArch spec in docs/phase-3-uarch/ must exist

If prerequisite is missing: WARNING — recommend running /rtl-agent-team:rtl-p3-uarch-design. Proceed with available artifacts — orchestrator will adapt scope.

Execution

# Step 1: Team creation (main session = leader)
TeamCreate(team_name="p4-implement", description="Phase 4 RTL implementation: 10-wave parallel module coding")

# Step 2: Write team-config.json for hook consumption
Write(".rat/state/team-config.json", json.dumps({
    "team_mode": true,
    "team_name": "p4-implement",
    "leader_session_id": "<current_session_id>",
    "coordinator_name": "coordinator",
    "worker_count": 4,
    "phase": "p4",
    "created_at": "<ISO_TIMESTAMP>"
}))

# Step 3: Prepare directories
Bash("mkdir -p reviews/phase-4-rtl docs/phase-4-rtl .rat/scratch/phase-4")

# Step 4: No initial tasks from skill — coordinator creates per-module W1-W10 after reading uarch specs

# Step 5: Spawn coordinator as teammate (orchestrator)
Agent(team_name="p4-implement", subagent_type="rtl-agent-team:p4-implement-team-orchestrator",
      name="coordinator", description="P4 implementation coordination",
      prompt="You are the Phase 4 RTL implementation coordinator in team 'p4-implement'. "
             "Manage the 10-wave task graph using TaskCreate/TaskList/TaskUpdate. "
             "Direct workers via SendMessage. "
             "Create per-module 10-wave task graph after reading uarch specs. "
             "Signal leader ONLY after the Phase 4 Gate (Step 4 — all required checks "
             "and artifacts, not merely the W10 integration gate) passes, including the "
             "mandatory Codex cross-review. User input: $ARGUMENTS")

# Step 6: Spawn workers as teammates (4 general-purpose)
Agent(team_name=, subagent_type=,
      name=, description=,
      prompt=
             
             
             
             
             
             
             )
Agent(team_name=, subagent_type=,
      name=, description=,
      prompt=
             
             
             
             
             
             )
Agent(team_name=, subagent_type=,
      name=, description=,
      prompt=
             
             
             
             
             
             )
Agent(team_name=, subagent_type=,
      name=, description=,
      prompt=
             
             
             
             
             )





 :
     coordinator_signaled_phase_complete:
        
        
        
    tasks = TaskList()
     (t.status ==   t  tasks):
        
        
        
    


TeamDelete()
Bash()
Bash()

Compliance Notes

• After each implementation wave completes (lint + unit test), invoke compliance-checker against P1+P2+P3 iron requirements
• RTL implementation must comply with all upstream iron requirements
• Per-wave compliance ensures regressions are caught before the integration gate (W10)