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.
Quick Reference
| Situation | Default pattern | Why |
|---|---|---|
| 1-2 tasks or shared-file edits | Stay in the main conversation | Parallelism adds coordination overhead without payoff |
| Focused worker that only needs to report back | Claude Code subagent or Codex worker | Isolated context, simple coordination |
| Workers must talk to each other | Claude Code agent team | Shared task list plus direct messaging |
| Read-heavy scans, tests, triage, summarization | Parallel workers | Keeps noisy intermediate output off the lead thread |
| One coordinator should retain user ownership | Manager / agents-as-tools | Lead keeps control of decisions and final answer |
| Specialist should take over the conversation | Handoff | Ownership moves to the specialist agent |
| Work of unknown extent — discovery is the task | Loop until K empty rounds | A fixed task list cannot be enumerated up front |
| Many items, known stages, high intermediate volume | Scripted workflow (Claude Code) | Script holds control flow; lead context holds only the result |