agents-swarm-orchestration
Swarm Orchestration
Coordinate multiple workers without polluting the main thread. Use this skill after ../agents-subagents/SKILL.md has already selected the right agent, member, team, or debate pattern. This skill is for choosing the orchestration surface, freezing task ownership before fan-out, and requiring structured outputs that the lead agent can validate and merge safely.
Terminology
"Swarm" is informal vocabulary for this skill, not the name of a portable runtime API. Use the official primitive names when writing configs, prompts, or docs; keep "swarm" only as informal shorthand for the whole category.
| Informal | Official primitive |
|---|---|
| "swarm of subagents" | Subagents |
| "swarm with peer chat" | Agent teams |
| "scripted swarm" | Dynamic workflows (script-held control flow) |
| "swarm across terminals" | Cross-session messaging |
Before sizing a run, look up each primitive's current status, platform availability, concurrency and per-run limits, background behavior, and recursion-depth default in the current Claude Code / Codex docs; the answer decides which primitive to launch and caps worker count and wave size. Launch mechanics live in ../agents-subagents/SKILL.md, the single owner of runtime facts.