Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
npx skills add https://github.com/michael-denyer/pstack-claude --skill swarm
On Codex, read the platform mapping, including its per-skill notes, before following this skill.
Fan out N parallel workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report.
Open a todolist with one entry per phase before launching anything.
first pass, rank all, or best-of before spawning.swarm workers in ~/.claude/pstack-models.md when present. Otherwise use the default in Models. For a model race, name each arm's model up front.Spawn all N workers in one message with subagent_type: "general-purpose", run_in_background: true, and the configured model. Claude Code subagents all run on this machine, so isolation comes from the worktree or output directory assigned in Phase A, not from a remote environment.
When a worker must start from a non-default branch, check that branch out in the worker's own worktree and name the worktree path 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.
If a worker drops out, proceed with N-1 and note it.
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.
Return one consolidated in-chat report with the table, issue one-liners, gaps or dropouts, and the race rule when used.
Role defaults, stamped from plugins/pstack/models.json (edit there, rerun tools/generate.mjs). A matching role line in ~/.claude/pstack-models.md overrides each at runtime; see /setup-pstack.
claude-opus-5Take michael-denyer/swarm from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.