Swarm

A skill named in bold or in backticks, or run as /<name>, is the file ../<name>/SKILL.md beside this skill's directory, and a principle named without its prefix is ../principle-<name>/SKILL.md. Read the file and follow it. Most pstack skills are user-only, so your skill tool cannot load them. Every delegate_task call follows the defaults in the Subagents section of ../poteto-mode/SKILL.md.

Start

Open a task list (your harness's task tool, or a checklist file at ~/.local/state/pstack/checklists/<repo>-<branch>.md when it has none) 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. Pick the worker model from the swarm workers line in ~/.config/pstack/pstack-models.md. An entry <providerInstanceId>/<model> (<effort>) becomes target: {"providerInstanceId": ..., "model": ..., "options": {"<effort option id>": "<effort>"}}, with the effort option id orchestrator_capabilities lists for that model. For auto or inherit-parent, or when the file or that line is missing, omit target so the workers run on the parent model. With no file, say so and suggest /setup-pstack. If delegate_task rejects an entry, use the closest model of the same provider that orchestrator_capabilities lists and say so. For a model race, name each arm's model up front. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the poteto-mode skill.
4. Give each worker its own writable output when it writes. When workers verify or measure commits, each brief names the exact SHAs. A measurement brief also names the method (sample count, what one sample is, order). The worker records both in its result.