Skip to content
  1. Wiki
  2. How pstack works
  3. /pstack:arena vs /pstack:swarm

/pstack:arena vs /pstack:swarm

/pstack:arena: several people solve the same problem, and the best wins. /pstack:swarm: a big job split into pieces, one each.

An analogy

/pstack:arena is a design pitch: pick one entry as the base and work in the others' best ideas. /pstack:swarm is grading exams: a hundred papers split among five teachers.

In pstack

Use /pstack:arena for decisions that are hard to change later, like names, formats and algorithms. Each candidate works on its own, and a model from another family judges them. Then it picks a base, adds the best parts of the others, and verifies. /pstack:architect uses it inside.

Use /pstack:swarm for jobs that must cover everything, like "check every package". Each helper handles its own piece and reports "pass / problem / blocked". At the end you get one short report.

Common misconceptions

  • "Use /pstack:arena for a full sweep": the pstack docs warn about this. For a full sweep, use /pstack:swarm. /pstack:arena would pick a base and merge parts for every result, which is wasted work.

Try it: Not sure which skill to use

Related: Subagents, The 24 principles

An unofficial beginner's guide to pstack, not its official docs. pstack is made by poteto; the official repo is the source of truth for commands and behavior. The original guide source is on GitHub.

Hosted by airali. Adapted from Xiaoxiaodong's MIT-licensed guide.