agents-swarm-orchestration
Installation
SKILL.md
Swarm Orchestration
Advanced execution layer for multi-worker runs after agent or team selection.
Coordinate multiple workers without polluting the main thread. Use this skill after agents-subagents 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 (Aug 2026)
"Swarm" is community vocabulary — it appears nowhere in Anthropic documentation. Use the official primitive names when writing configs, prompts, or docs; keep "swarm" only as informal shorthand for the whole category.
| Informal | Official primitive | Status (Aug 2026) |
|---|---|---|
| "swarm of subagents" | Subagents | GA. Background behavior is mode-dependent; background: true forces background but false is not a documented foreground pin. Recursive spawn currently defaults to three layers below the main session |
| "swarm with peer chat" | Agent teams | Experimental, env-gated CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. Behavior churns weekly — re-verify before relying |
| "scripted swarm" | Dynamic workflows | Shipped 2026-05. JS in .claude/workflows/; ≤1000 agents/run, 16 concurrent. The repeatable-orchestration artifact |
| "swarm across terminals" | Cross-session messaging | Aug 2026, macOS/Linux. Sessions message each other without a team — lighter than teams for passing findings |