---
name: dsp
description: Dispatch subagents in parallel for implementation tasks
---

# DSP -- Dispatch Subagents in Parallel

Parallel agent dispatch for implementation tasks. Orchestrate, then delegate to subagents.

**Usage:** `/dsp <instructions>`

## Rules

1. **Always dispatch, never self-execute** -- the purpose is to offload work to subagents
2. **Parallel within waves** -- all agents in a wave dispatched in a SINGLE message
3. **Orient first** -- read `.claude/rules/agent-start-here.md` before planning to understand project structure and task routing

## Process

### Step 1: Understand Context

1. Read `.claude/rules/agent-start-here.md` for project structure, task-class routing, and boundary resolution
2. Read relevant architecture/feature docs based on the task domain
3. If the task touches code, explore the relevant `src/` directories

### Step 2: Analyze Complexity

**Single-Wave** -- all tasks independent, dispatch everything at once
**Multi-Wave** -- tasks have dependencies, execute waves sequentially

### Step 3: Plan

For each unit of work, identify:

- What files/areas are affected
- What context the subagent needs
- Whether it depends on another task's output

Print the plan:

```
DSP Plan: N waves, M tasks
Wave 1: [description] -- N tasks
Wave 2: [description] -- N tasks (if multi-wave)
Dispatching Wave 1...
```

### Step 4: Dispatch

Use the Agent tool with `subagent_type="general-purpose"` and `model="sonnet"`.

Each agent prompt must include:

- The specific task to accomplish
- Relevant file paths and context
- Instruction to use backslash paths for file operations on Windows

### Step 5: Aggregate Results

```
DSP Results: [description]

Tasks completed: X/Y
Files modified: [list]
Next steps: [if any]
```
