rtl-p2-arch-team

name	rtl-p2-arch-team
description	Phase 2 architecture with parallel team workers: dual-stream arch + RefC development. Use for 'arch team', 'Phase 2 team', 'parallel architecture'.
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 2 architecture 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 1 research is complete and architecture design is needed
• User says "arch team", "Phase 2 team", "parallel architecture"
• Have multiple algorithm candidates requiring parallel HW evaluation
• Need maximum parallelism for dual-stream arch + RefC development </Use_When>

<Do_Not_Use_When>

• Phase 1 research not complete (run p1-spec-research first)
• Single candidate only (use p2-arch-design for simpler flow)
• Only need reference model (use ref-model) </Do_Not_Use_When>

Prerequisites

Phase 1 completion required:

• docs/phase-1-research/iron-requirements.json must exist
• docs/phase-1-research/open-requirements.json (optional — absent if P1 had no open items)
• docs/phase-1-research/io_definition.json must exist

If prerequisites are missing: WARNING — recommend running /rtl-agent-team:p1-spec-research. Proceed with available artifacts — orchestrator will adapt scope.

Execution

# Step 1: Team creation (main session = leader)
TeamCreate(team_name="p2-arch", description="Phase 2 architecture: dual-stream arch + RefC development")

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

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

# Step 4: No initial tasks from skill — coordinator creates T1a-N after reading P1 artifacts

# Step 5: Spawn coordinator as teammate (orchestrator)
Agent(team_name="p2-arch", subagent_type="rtl-agent-team:p2-arch-team-orchestrator",
      name="coordinator", description="P2 architecture coordination",
      prompt="You are the Phase 2 architecture coordinator in team 'p2-arch'. "
             "Manage the task graph using TaskCreate/TaskList/TaskUpdate. "
             "Direct workers via SendMessage. "
             "Create all tasks (T1a-N HW eval through T13 final consolidation), then perform "
             "Step 3.7/3.8 iron/open artifact production (REQ-A-* from resolved OPEN-1-*) + open "
             "resolution + ambiguity gate, then T14 compliance. "
             "Signal leader ONLY after the Phase 2 Gate (Step 4) passes — including the "
             "Step 3.9 compliance check, ADR generation, and the mandatory Codex cross-review. "
             )


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-1-* items from Phase 1 open-requirements.json
• Exit gate includes open-resolved, compliance-pass (compliance-checker vs P1 iron, orchestrator Step 3.9), and ambiguity-pass