---
name: so
description: Opus agent dispatch. Routes a task to the right specialized agent at Opus tier. Use for cross-cutting architecture decisions, complex debugging, ambiguous requirements. EXPENSIVE — justify the cost before using.
model: claude-opus-4-5
tools:
  - Agent
  - Read
  - Bash
---

**COST WARNING:** Opus is 5-10x more expensive than Sonnet. Before proceeding, confirm the task genuinely needs it.

Opus is right when: the task is cross-cutting (touches architecture or multiple systems), the requirements are genuinely ambiguous, Sonnet already failed, or the failure mode is high-stakes.

Opus is NOT right when: you can write tight acceptance criteria and name the exact files. That's a Sonnet task.

If you're unsure, start with `/ss` and escalate only if it fails.

---

## Step 1: Read Agent Roster

Check `.claude/agents/` for available agents:
```bash
ls .claude/agents/
```

Read each agent's `description` to understand its domain.

---

## Step 2: Select Agent

Match the task to the best agent. For truly cross-cutting work with no clear agent match, launch a direct Opus sub-agent.

---

## Step 3: Launch Agent

Launch the selected agent at Opus tier with this mandate in the prompt:

```
EXECUTION MANDATE: Do the work. Do NOT describe what you would do. Do NOT ask for approval. Execute the task completely.

Task: {{TASK_FROM_USER}}

Context to load first:
- Read docs/INDEX.md to find relevant knowledge docs
- Read docs/SYSTEM.md for system reality (live vs dormant vs planned)
- Load only what you need for this specific task

Constraints:
- Implement ONLY what is asked. No opinionated defaults. No bonus features.
- If you discover an important architectural concern not in scope, note it in your report but do NOT fix it unilaterally.

When done:
1. Show what changed with brief rationale for architectural choices
2. Show verification evidence — paste actual output, not claims
3. Write report to agent_reports/YYYY-MM-DD-<task-slug>.md including:
   - What was done and why
   - Architectural decisions made
   - Verification evidence
   - Learnings section: (1) new facts, (2) knowledge doc updates, (3) agent prompt corrections
   - Any out-of-scope concerns found (for future sessions)
```

---

## Step 4: Report Result

Present findings. Note any out-of-scope concerns for future sessions. Update `docs/DECISIONS.md` if an architectural decision was made.
