
Swarm Orchestration
- 1k installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
swarm orchestration is an agent skill that initializes and monitors a hierarchical multi-agent swarm via @claude-flow/cli for developers whose features or refactors span many files and modules.
About
swarm orchestration is a skill from ruvnet/ruflo for multi-agent swarm coordination on complex tasks. Bundled bash scripts run npx @claude-flow/cli swarm init with hierarchical topology, max-agents 8, and specialized strategy, then monitor status on a 5-second interval. A separate monitor script watches swarm health in real time. Developers reach for swarm orchestration when a feature or refactor touches many files and modules and needs specialized agents under anti-drift defaults rather than a single monolithic agent pass.
- Initializes hierarchical swarms with configurable max agents and specialized strategy
- Targets 3+ file changes, cross-module refactors, and API changes with tests
- Includes monitor workflow with watch-mode swarm status polling
- Explicit skip rules for single-file edits, tiny fixes, and doc-only updates
Swarm Orchestration by the numbers
- 1,044 all-time installs (skills.sh)
- Ranked #1,011 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill swarm-orchestrationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 67k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you orchestrate multi-agent swarms for large refactors?
Coordinate a hierarchical multi-agent swarm when a feature or refactor touches many files and modules.
Who is it for?
Developers running @claude-flow/cli who need hierarchical swarms for large cross-module features or refactors.
Skip if: Small single-file edits or teams using only Claude Code's native Agent Tool without claude-flow CLI.
When should I use this skill?
A feature or refactor spans many files and modules and needs hierarchical multi-agent swarm coordination.
What you get
Initialized hierarchical swarm, running specialized agents, and real-time swarm status monitor output.
- initialized swarm
- agent task breakdown
- live swarm status output
By the numbers
- Initializes swarms with max-agents 8
- Monitors swarm status on a 5-second interval
Files
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 specializedExample:
npx @claude-flow/cli swarm init --topology hierarchical --max-agents 6 --strategy specializedRoute 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-authMonitor Status
Check the current swarm status
npx @claude-flow/cli swarm status --verboseOrchestrate Task
Orchestrate a task across multiple agents
npx @claude-flow/cli task orchestrate --task "[task]" --strategy adaptiveExample:
npx @claude-flow/cli task orchestrate --task "refactor auth module" --strategy parallel --max-agents 4List Agents
List all active agents
npx @claude-flow/cli agent list --filter activeScripts
| 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
1. Check memory for existing patterns before starting 2. Use hierarchical topology for coordination 3. Store successful patterns after completion 4. Document any new learnings
#!/bin/bash
# Swarm Orchestration - Monitor Script
# Real-time swarm monitoring
set -e
echo "Starting swarm monitor..."
npx @claude-flow/cli swarm status --watch --interval 5
#!/bin/bash
# Swarm Orchestration - Start Script
# Initialize swarm with default anti-drift settings
set -e
echo "Initializing hierarchical swarm..."
npx @claude-flow/cli swarm init \
--topology hierarchical \
--max-agents 8 \
--strategy specialized
echo "Swarm initialized successfully"
npx @claude-flow/cli swarm status
Related skills
How it compares
Use swarm orchestration for claude-flow CLI hierarchical swarms; use parallel-agents for native Claude Code Agent Tool orchestration.
FAQ
What CLI does swarm orchestration use?
swarm orchestration uses npx @claude-flow/cli swarm commands to init hierarchical swarms and watch status. Init sets topology hierarchical, max-agents 8, and strategy specialized with anti-drift defaults.
How does swarm orchestration monitor agents?
swarm orchestration monitors agents by running npx @claude-flow/cli swarm status --watch --interval 5 after initialization, providing real-time swarm health output during multi-file coordinated work.
Is Swarm Orchestration safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.