Squad — parallel subagent dispatcher

This is a rare-case tool. Worktrees and parallel dispatch are overhead. Use squad only when the goal is genuinely big AND splits into clearly independent pieces, each substantial on its own. For ordinary work, refuse with "this doesn't need squad — do it directly."

For one big task that splits cleanly into N≥2 independent pieces. Run them in parallel; cherry-pick the results.

Squad is fan-out, not a pipeline. No dependencies, no ordering, no resume. If pieces depend on each other, merge them or do it yourself.

You already know the Agent tool, git, and worktrees. This is the contract.

Flow

1. Decompose the goal into N≥2 sibling tasks with disjoint writable files.
2. Plan: emit the task list as JSON in chat — this lets you mechanically verify the constraints. Refuse if N<2 or any two tasks share a path in files.