dispatch-agentslisted

# Dispatch Agents > **HARD GATE** — **HARD GATE** — Agent work must be parallelizable and have explicit synchronization points. Do NOT dispatch work that has hidden dependencies between agents. Run multiple subagents in parallel on independent tasks. Use when tasks are genuinely decoupled — no agent needs the output of another to start. **Distinct from `delegate-task`:** This skill maximizes throughput via concurrency. There is no sequential review gate between tasks. Use `delegate-task` instead when a single task needs careful two-stage oversight before proceeding. ## When to use - Tasks that can run simultaneously without shared state - Large plans that can be broken into parallel workstreams - Exploration: gather information from multiple parts of the codebase at once ## When NOT to use - Task B depends on Task A's output - You need to review Task A before Task B can start safely - The tasks share a file and concurrent edits would conflict ## Process ### 1. Confirm independence Before dispatching, verify each task pair is truly independent: - No shared files being written - No shared state (DB migrations, config files) - No ordering dependency between outcomes If any two tasks conflict, sequence them with `delegate-task` or `execute-plan` instead. ### 2. Write task briefs Before writing briefs, read `specs/state.yaml` if it exists — each agent gets only the decisions relevant to its task, nothing else. For each task, use this minimal template (each agent star