Orchestrates swarms of specialized agents to handle large, multi-file code changes.
Install
mkdir -p .claude/skills/swarm-orchestration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1978" && unzip -o skill.zip -d .claude/skills/swarm-orchestration && rm skill.zipInstalls to .claude/skills/swarm-orchestration
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules. Use when: 3+ files need changes, new feature implementation, cross-module refactoring, API changes with tests, security-related changes, performance optimization across codebase, database schema changes. Skip when: single file edits, simple bug fixes (1-2 lines), documentation updates, configuration changes, quick exploration.Key capabilities
- →Initialize hierarchical agent swarms
- →Route tasks to specialized agents
- →Orchestrate complex cross-module tasks
- →Monitor swarm status
- →Spawn specialized agent types
How it works
It uses a hierarchical topology to decompose complex tasks into sub-tasks, assigning them to specialized agents for coordinated execution.
Inputs & outputs
When to use swarm-orchestration
- →Execute cross-module refactoring
- →Implement complex new features
- →Perform large-scale code updates
About this skill
Swarm Orchestration Skill
Purpose
Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules.
When to Trigger
- 3+ files need changes
- new feature implementation
- cross-module refactoring
- API changes with tests
- security-related changes
- performance optimization across codebase
- database schema changes
When to Skip
- single file edits
- simple bug fixes (1-2 lines)
- documentation updates
- configuration changes
- quick exploration
Commands
Initialize Swarm
Start a new swarm with hierarchical topology (anti-drift)
npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8 --strategy specialized
Example:
npx @claude-flow/cli swarm init --topology hierarchical --max-agents 6 --strategy specialized
Route Task
Route a task to the appropriate agents based on task type
npx @claude-flow/cli hooks route --task "[task description]"
Example:
npx @claude-flow/cli hooks route --task "implement OAuth2 authentication flow"
Spawn Agent
Spawn a specific agent type
npx @claude-flow/cli agent spawn --type [type] --name [name]
Example:
npx @claude-flow/cli agent spawn --type coder --name impl-auth
Monitor Status
Check the current swarm status
npx @claude-flow/cli swarm status --verbose
Orchestrate Task
Orchestrate a task across multiple agents
npx @claude-flow/cli task orchestrate --task "[task]" --strategy adaptive
Example:
npx @claude-flow/cli task orchestrate --task "refactor auth module" --strategy parallel --max-agents 4
List Agents
List all active agents
npx @claude-flow/cli agent list --filter active
Scripts
| Script | Path | Description |
|---|---|---|
swarm-start | .agents/scripts/swarm-start.sh | Initialize swarm with default settings |
swarm-monitor | .agents/scripts/swarm-monitor.sh | Real-time swarm monitoring dashboard |
References
| Document | Path | Description |
|---|---|---|
Agent Types | docs/agents.md | Complete list of agent types and capabilities |
Topology Guide | docs/topology.md | Swarm topology configuration guide |
Best Practices
- Check memory for existing patterns before starting
- Use hierarchical topology for coordination
- Store successful patterns after completion
- Document any new learnings
When not to use it
- →Single file edits
- →Simple bug fixes
- →Documentation updates
Prerequisites
Limitations
- →Overhead is high for simple tasks
- →Requires defined agent types and topology
How it compares
It provides structured multi-agent coordination for large-scale changes, whereas manual orchestration lacks standardized agent roles and topology.
Compared to similar skills
swarm-orchestration side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| swarm-orchestration (this skill) | 2 | 6mo | Review | Advanced |
| agent-factory | 8 | 9mo | Review | Advanced |
| claude-opus-4-5-migration | 9 | 8mo | No flags | Beginner |
| subagent-driven-development | 14 | 7mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ruvnet
View all by ruvnet →You might also like
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
claude-opus-4-5-migration
anthropics
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.
subagent-driven-development
davila7
Use when executing implementation plans with independent tasks in the current session
coding-agent
openclaw
Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
continuous-learning-v2
affaan-m
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
copilot-sdk
github
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.