swarm-orchestration
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.
Profile →npx skills add ruvnet/ruflo --skill swarm-orchestration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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) ```bash npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8 --strategy specialized ``` **Example:** ```bash 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 ```bash npx @claude-flow/cli hooks route --task "[task description]" ``` **Example:** ```bash npx @claude-flow/cli hooks route --task "implement OAuth2 authentication flow" ``` ### Spawn Agent Spawn a specific agent type ```bash npx @claude-f
- Purpose
- When to Trigger
- When to Skip
- Commands
- Initialize Swarm
- Route Task
- Spawn Agent
- Monitor Status
- Orchestrate Task
- List Agents
- Scripts
- References
- Best Practices
npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8 --strategy specialized npx @claude-flow/cli swarm init --topology hierarchical --max-agents 6 --strategy specialized npx @claude-flow/cli hooks route --task "[task description]" npx @claude-flow/cli hooks route --task "implement OAuth2 authentication flow" npx @claude-flow/cli agent spawn --type [type] --name [name] npx @claude-flow/cli agent spawn --type coder --name impl-auth npx @claude-flow/cli swarm status --verbose npx @claude-flow/cli task orchestrate --task "[task]" --strategy adaptive npx @claude-flow/cli task orchestrate --task "refactor auth module" --strategy parallel --max-agents 4 npx @claude-flow/cli agent list --filter active
What does the swarm-orchestration skill do?
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.
How do I install it?
Run `npx skills add ruvnet/ruflo --skill swarm-orchestration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.