Rtl P5 Verify Team

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="rtl-agent-team:func-verifier",
      name="verify-0", description="P5 functional verification",
      prompt="You are a Phase 5 verification worker in team 'p5-verify'. "
             "Coordinator: 'coordinator' (send results via SendMessage). "
             "Phase artifacts: reviews/phase-5-verify/, sim/. "
             "Specialty: lint (V1), functional regression (V5), coverage (V6). "
             "For specialist work, spawn: Task(subagent_type='rtl-agent-team:<specialist>', prompt='...'). "
             "Examples: lint-checker for V1, testbench-dev for TB, eda-runner for sim, coverage-analyst for V6. "
             "Follow the Team Worker Protocol section of your agent definition.")
Agent(team_name="p5-verify", subagent_type="rtl-agent-team:sva-extractor",
      name="verify-1", description="P5 formal and CDC verification",
      prompt="You are a Phase 5 verification worker in team 'p5-verify'. "
             "Coordinator: 'coordinator' (send results via SendMessage). "
             "Phase artifacts: formal/, lint/cdc/, reviews/phase-5-verify/. "
             "Specialty: SVA/formal (V2), CDC (V3), protocol (V4). "
             "For specialist work, spawn: Task(subagent_type='rtl-agent-team:<specialist>', prompt='...'). "
             "Examples: cdc-checker for V3, protocol-checker for V4, constraint-writer for SDC. "
             "Follow the Team Worker Protocol section of your agent definition.")
Agent(team_name="p5-verify", subagent_type="rtl-agent-team:eda-runner",
      name="analysis-worker", description="P5 performance and synthesis",
      prompt="You are a Phase 5 analysis worker in team 'p5-verify'. "
             "Coordinator: 'coordinator' (send results via SendMessage). "
             "Phase artifacts: reviews/phase-5-verify/. "
             "Specialty: performance (V7), synthesis estimation (V8). "
             "For specialist work, spawn: Task(subagent_type='rtl-agent-team:<specialist>', prompt='...'). "
             "Examples: perf-verifier for V7, synthesis-reporter for V8. "
             "Follow the Team Worker Protocol section of your agent definition.")
Agent(team_name="p5-verify", subagent_type="rtl-agent-team:rtl-critic",
      name="review-worker", description="P5 code review and compliance",
      prompt="You are a Phase 5 review worker in team 'p5-verify'. "
             "Coordinator: 'coordinator' (send results via SendMessage). "
             "Phase artifacts: reviews/phase-5-verify/. "
             "Specialty: code review (V9), requirement traceability, final compliance. "
             "For specialist work, spawn: Task(subagent_type='rtl-agent-team:<specialist>', prompt='...'). "
             "Examples: requirement-tracer for REQ mapping, rtl-critic for review. "
             "Follow the Team Worker Protocol section of your agent definition.")

# Step 7: Leader wait — teardown is gated on the COORDINATOR SIGNAL, not on TaskList.
# "All tasks completed" is necessary but NOT sufficient: the coordinator's post-gate
# work (compliance check, ADR generation, phase summary, Codex cross-review) runs via
# direct Task() calls that never appear in the shared task graph.
while True:
    if coordinator_signaled_phase_complete:
        # SendMessage from 'coordinator' — sent only after the phase gate
        # AND all post-gate mandatory steps pass (see coordinator prompt above)
        break
    tasks = TaskList()
    if all(t.status == "completed" for t in tasks):
        # Task graph drained but no coordinator signal yet → the coordinator is
        # still running gate/post-gate steps. KEEP WAITING — do NOT TeamDelete.
        pass
    # Continue polling

# Step 8: Cleanup
TeamDelete()
Bash("rm -f .rat/state/team-config.json")
Bash("rm -rf .rat/scratch/phase-5/")

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