Swarm
Fan out N parallel cloud workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report.
Start
Open a todolist with one entry per phase before launching anything.
- Frame
- Fan out
- Aggregate
- Report
Phase A: Frame
- State the done predicate and the artifact or report the swarm must return.
- Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare , , or before spawning.
- Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit.
- Pick the worker model from in
~/.cursor/rules/pstack-models.mdc
when present. Otherwise use . For a model race, name each arm's model up front.
- Give each worker its own writable output when it writes. Use a worktree, branch, or
/tmp/swarm-<slug>/worker-<n>/
.
Phase B: Fan out
Spawn all N workers in one message with
subagent_type: generalPurpose
,
,
, and the configured model. Use
only when the worker needs access to something on the user's computer.
When a worker must start from a non-default pushed branch, pass
.
Every brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use
,
, or
with evidence.
If a worker drops out, proceed with N-1 and note it.
Phase C: Aggregate
Read the terminal results. For coverage, every required slice needs a result. For a race, apply the selection rule declared up front. Use first pass, rank all, or best-of. Do not paste raw worker dumps.
Keep a compact result table, one-line evidenced issues, and explicit gaps or dropouts.
Phase D: Report
Return one consolidated in-chat report with the table, issue one-liners, gaps or dropouts, and the race rule when used.