rtl-p5-verify-team

name	rtl-p5-verify-team
description	Phase 5 verification with native team parallel workers across modules. Triggers 'verify team', 'parallel verify', 'Phase 5 team'; best for 3+ modules.
user-invocable	true
argument-hint	[--module=name | --resume]
allowed-tools	Bash, Read, Write, Edit, Task, Grep, Glob, TeamCreate, TeamDelete, Agent, SendMessage, TaskCreate, TaskList, TaskUpdate, AskUserQuestion

Execute Phase 5 verification 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 9-category verification task graph and directs workers via SendMessage.

<Use_When>

• Phase 4 RTL implementation is complete with lint passing
• User says "verify team", "Phase 5 team", "parallel verify"
• Need maximum parallelism for multi-module verification
• Have 3+ modules that benefit from concurrent verification workers </Use_When>

<Do_Not_Use_When>

• RTL modules don't exist yet (run rtl-p4-implement first)
• Single module only (use rtl-p5-verify for simpler flow)
• Want sequential verification (use rtl-p5-verify)
• Only need a specific verification category (use the category-specific skill) </Do_Not_Use_When>

Prerequisites

Phase 4 completion required:

• rtl/**/*.sv files must exist
• One of the following completion proofs must exist:
  • reviews/phase-4-rtl/lint-report.md (full rtl-p4-implement path)
  • .rat/state/p4-state.json with gates.p4_exit.verdict = pass (rapid rtl-p4-rapid-impl path)

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

Execution

# Step 1: Team creation (main session = leader)
TeamCreate(team_name="p5-verify", description="Phase 5 verification: 9-category parallel verification")

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

# Step 3: Prepare directories
Bash("mkdir -p docs/phase-5-verify reviews/phase-5-verify sim/coverage formal lint/cdc .rat/scratch/phase-5")

# Step 4: No initial tasks from skill — coordinator creates per-module V1-V9 after discovering modules

# Step 5: Spawn coordinator as teammate (orchestrator)
Agent(team_name="p5-verify", subagent_type="rtl-agent-team:p5-verify-team-orchestrator",
      name="coordinator", description="P5 verification coordination",
      prompt="You are the Phase 5 verification coordinator in team 'p5-verify'. "
             "Manage the 9-category task graph using TaskCreate/TaskList/TaskUpdate. "
             "Direct workers via SendMessage. "
             "Create per-module V1-V9 task graph after discovering modules. "
             "Signal leader ONLY after final compliance, the Phase 5 summary task (S3.5), "
             "and the mandatory Codex cross-review (Step 6) are ALL complete. "
             "User input: $ARGUMENTS")

# Step 6: Spawn workers as teammates (4 general-purpose)
Agent(team_name="p5-verify", 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

• Verification must confirm all iron requirement acceptance_criteria are met. When structured acceptance_criteria (with ac_id) exist from P3, verification tracks compliance at the individual criterion level (ac_id granularity). When acceptance_criteria is in string-array format (P1/P2), verification operates at REQ level.
• Final compliance check compares test results against P1+P2+P3 acceptance_criteria
• Phase 5 PASS requires zero unmet iron requirements across all verification categories