swarm

Imported from Whamp/pi-extensions (packages/pi-pstack/skills/swarm/SKILL.md). Install upstream with npx skills add Whamp/pi-extensions --skill swarm. Copyright stays with the author.

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.

1. Frame
2. Fan out
3. Aggregate
4. Report

Phase A: Frame

1. State the done predicate and the artifact or report the swarm must return.
2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare first pass, rank all, or best-of before spawning.
3. Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit.
4. Pick the worker model from swarm workers in ~/.pi/agent/pstack/models.json when present. Otherwise use inherit-parent. For a model race, name each arm's model up front.
5. Give each worker its own writable output when it writes.

Phase B: Fan out

Launch all N workers with one subagent({ action: "execute", input: { async: true, maxSubagentSpawnsPerRun: N, workflowScript } }) call. In workflowScript, use return await runs.all([{ key: "worker-<slice>", agent: "worker", task, model }]). Give each worker a stable key and the configured model. Omit model when the role inherits the parent.

Set input.cwd to an existing checkout. To create a managed checkout from a Git ref, set input.worktree: true and input.baseRef.

Every brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use PASS, ISSUES, or BLOCKED 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.