Swarm
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
first pass,rank all, orbest-ofbefore spawning. - Pick the worker model from the
swarm workersline in~/.zcode/pstack/models.md. If the file or that line is missing, use the session model. Forinherit-parent, omitmodelso the workers run on the parent model. If the spawn rejects a model, use the default and say so. If it rejects the default, use the closest valid model of the same family from its error message. For a model race, name each arm's model up front. Pick each subagent's reasoning level and reasoning level for the job, per the Subagents section of the pstack-poteto-mode skill. - 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.
Phase B: Fan out
The swarm fans out through a dynamic workflow: one worker subagent per brief, each on the step 4 model with its entry's reasoning level, its arm's model in a model race, model omitted for inherit-parent so those workers run on the session model.
Load the dynamic-workflows skill, generate the workflow and save it once (pstack-swarm, global scope), and re-run it by name on later runs, passing the model table and the briefs as workflow arguments so each run approves arguments against the saved script; regenerate and re-save when the configured models change.
When a worker must start from a non-default pushed branch, name the branch in its brief.
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. A worker that can prove a defect reports ISSUES and lists every issue it can prove, not only the first.
If a worker drops out, proceed with N-1 and note it.
Phase C: Aggregate
Read the terminal results. Drop a result that does not record the SHAs and method its brief names, and respawn that worker once. After a second miss, record a gap. A gap does not count as a pass. 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.
Phase D: Report
Return one consolidated in-chat report with a result table, issue one-liners, gaps or dropouts, and the race rule when used.