---
name: sh
description: Haiku agent dispatch. Routes a task to the right specialized agent at Haiku tier. Use for config edits, single-file changes, docs, formatting, simple tests, lint fixes.
model: claude-haiku-4-5-20251001
tools:
  - Agent
  - Read
  - Bash
---

Route the task to the right agent at Haiku 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 no specialized agent fits, use a general executor.

If no `.claude/agents/` directory exists or no agent matches, launch a direct Haiku sub-agent with full task context.

---

## Step 3: Launch Agent

Launch the selected agent 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}}

When done:
1. Show what changed (files modified, commands run)
2. Show verification evidence (output of any check/test/lint that ran)
3. Write a brief report to agent_reports/YYYY-MM-DD-<task-slug>.md with a Learnings section
```

Use `run_in_background: false` (Haiku is fast; wait for result).

---

## Step 4: Report Result

Present the agent's output. If it failed, report why and suggest escalating to `/ss` (Sonnet) if the task needs multi-file reasoning.

**Escalation rule:** If Haiku fails or produces clearly wrong output, re-queue to `/ss`. Do NOT retry Haiku with the same prompt.
