rtl-p3-uarch-team

name	rtl-p3-uarch-team
description	Phase 3 uArch with parallel team workers: dual-stream per-block uArch + BFM development. Use for 'uarch team', 'Phase 3 team', 'parallel uarch'.
user-invocable	true
argument-hint	[--resume]
allowed-tools	Bash, Read, Write, Edit, Task, Grep, Glob, TeamCreate, TeamDelete, Agent, SendMessage, TaskCreate, TaskList, TaskUpdate, AskUserQuestion

Execute Phase 3 uArch design 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 task graphs and directs workers via SendMessage.

<Use_When>

• Phase 2 architecture is complete and uArch design is needed
• User says "uarch team", "Phase 3 team", "parallel uarch"
• Have multiple modules requiring parallel uarch design
• Need maximum parallelism for dual-stream uArch + BFM development </Use_When>

<Do_Not_Use_When>

• Phase 2 architecture not complete (run p2-arch-design first)
• Single module only (use rtl-p3-uarch-design for simpler flow)
• Only need BFM (use bfm-develop) </Do_Not_Use_When>

Prerequisites

Phase 2 completion required:

• docs/phase-2-architecture/architecture.md must exist
• refc/ directory with C reference model must exist

If prerequisites are missing: WARNING — recommend running /rtl-agent-team:p2-arch-design. Proceed with available artifacts — orchestrator will adapt scope.

Execution

# Step 1: Team creation (main session = leader)
TeamCreate(team_name="p3-uarch", description="Phase 3 uArch: dual-stream uArch + BFM development")

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

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

# Step 4: Create initial task graph (T1 and T2 are independent — no dependencies)
TaskCreate(subject="T1: uArch Design",
           description="Per-block micro-architecture design from architecture spec")
TaskCreate(subject="T2: BFM Development",
           description="Bus Functional Model development from architecture spec")

# Step 5: Spawn coordinator as teammate (orchestrator)
Agent(team_name="p3-uarch", subagent_type="rtl-agent-team:p3-uarch-team-orchestrator",
      name="coordinator", description="P3 uArch coordination",
      prompt="You are the Phase 3 uArch coordinator in team 'p3-uarch'. "
             "Manage the task graph using TaskCreate/TaskList/TaskUpdate. "
             "Direct workers via SendMessage. "
             "Initial tasks T1 (uarch) and T2 (BFM) already created by leader. "
             "Create dynamic tasks (T3 BFM gate, T4-T10 review rounds), then perform Step 3.7/3.8 "
             
             
             
             
             )


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()

Workflow Notes

• Open Resolution: resolve all OPEN-2-* items from Phase 2 open-requirements.json
• Zero-Opens Invariant: no unresolved OPEN-* items may pass to Phase 4
• Exit gate includes open-resolved, zero-remaining-opens, and ambiguity-pass
• Exit gate includes compliance-pass (compliance-checker vs P1+P2 iron, orchestrator Step 3.9)