---
name: ss
description: Sonnet agent dispatch. Routes a task to the right specialized agent at Sonnet tier. Use for features, bugfixes, multi-file changes, refactors, code review.
model: claude-sonnet-4-5
tools:
  - Agent
  - Read
  - Bash
---

Route the task to the right agent at Sonnet tier.

**Execution mandate:** The agent you launch MUST do the work. Do NOT describe what you would do. Do NOT make a plan and ask for approval. Execute.

---

## Step 1: Read Agent Roster

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

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

---

## Step 2: Select Agent

Match the task to the best agent based on its domain.

If the task spans multiple domains (e.g. backend + frontend), consider launching two sequential agents — backend first, then frontend — rather than one overloaded agent.

If no specialized agent fits, launch a direct Sonnet sub-agent with full task context.

---

## Step 3: Launch Agent

Launch the selected agent at Sonnet 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
- Load only what you need, not everything

When done:
1. Show what changed (files modified, commands run, diffs if useful)
2. Show verification evidence (test output, lint output, or verify script result — paste actual output)
3. Write report to agent_reports/YYYY-MM-DD-<task-slug>.md including:
   - What was done
   - Verification evidence
   - Learnings section: (1) new facts discovered, (2) knowledge doc updates needed, (3) agent prompt corrections
```

---

## Step 4: Report Result

Present the agent's findings. Extract any learnings and note which knowledge docs need updating.

If the task requires architectural decisions or cross-cutting reasoning beyond Sonnet's scope, suggest escalating to `/so`.
