dispatching-parallel-agentslisted

# Dispatching Parallel Agents ## Pre-Dispatch: Read Preferences Before any dispatch, read `.sixth-sense/model-preferences.md` from the project root. If the file does not exist, use defaults: Sonnet medium, **Haiku batching enabled** for the `haiku-batch` tier only (the eligibility bar below is already the guardrail — narrow it further, don't widen it), max 4 agents, **Opus routing enabled** (`opus-high` tier, see Effort Routing below and `opus-routing: false` to disable). Opus routing is distinct from `opus-review`: `opus-review` is a narrow, always-separate read-only second-opinion pass in `specifying-and-implementing`'s Spec phase/`requesting-code-review`, never used for dispatch; `opus-high` is a normal Effort Routing tier, dispatched like any other tier, reserved for genuinely architectural work and the fix loop's last-resort escalation (see Post-Dispatch). See `configuring-sixth-sense`. Run `/setup-sixth-sense` to change these defaults (e.g. to turn Haiku batching or Opus routing off entirely), not to unlock them. ## When to Dispatch Dispatch parallel subagents only when: * **Independence:** Tasks have no shared state or sequential dependencies (they do not modify the same files or rely on each other's output). * **Workload:** The total volume of work is significant or benefits from parallel execution. * **Complexity:** The task can be cleanly decomposed into distinct, non-overlapping workstreams. If tasks are sequential or tightly coupled, execute them iteratively.