Agent Coordination
- 1k installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
agent-coordination is a Ruflo agent skill that spawns, monitors, and coordinates specialized multi-agent pools for developers tackling complex software projects requiring parallel coder, reviewer, tester, and planner age
About
agent-coordination is a Ruflo skill for spawning, lifecycle management, and coordination patterns across 60+ specialized agent types. Core development roles include `coder`, `reviewer`, `tester`, `planner`, and `researcher`; V3 roles add `security-architect`, `security-auditor`, `memory-specialist`, and `performance-engineer`; swarm roles include `hierarchical-coordinator`, `mesh-coordinator`, and `adaptive-coordinator`. Developers reach for agent-coordination when a task needs parallel specialists—security review while coding, or coordinated swarms—not a single general agent. The skill says to skip it for simple single-agent work with no coordination overhead.
- Manages 60+ agent types including coder, reviewer, tester, planner, researcher, security-architect, and sparc variants
- Supports hierarchical, mesh, adaptive, and collective-intelligence swarm coordination patterns
- Provides spawn, list, status, metrics, stop, and pool management commands
- Includes consensus mechanisms such as byzantine, raft, and gossip coordinators
- Integrates GitHub workflows with pr-manager, code-review-swarm, and release-manager agents
Agent Coordination by the numbers
- 1,047 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #996 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill agent-coordinationAdd 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 coordinate multiple specialized coding agents?
Spawn, monitor, and coordinate multiple specialized agents for complex software projects.
Who is it for?
Developers running Ruflo who need orchestration across dozens of specialist agent types for large parallel software efforts.
Skip if: Single-agent tasks with no parallel roles, spawning, or pool management requirements.
When should I use this skill?
The user asks to spawn agents, coordinate a multi-agent swarm, or assign coder, reviewer, tester, and planner roles in Ruflo.
What you get
A managed multi-agent pool with assigned roles, lifecycle state, and coordinated task outputs.
- Spawned agent pool
- Coordinated multi-agent task plan
By the numbers
- Manages 60+ specialized agent types
Files
Agent Coordination Skill
Purpose
Spawn and coordinate agents for complex multi-agent tasks.
Agent Types
Core Development
coder, reviewer, tester, planner, researcher
V3 Specialized
security-architect, security-auditor, memory-specialist, performance-engineer
Swarm Coordination
hierarchical-coordinator, mesh-coordinator, adaptive-coordinator, collective-intelligence-coordinator
Consensus
byzantine-coordinator, raft-manager, gossip-coordinator, consensus-builder
GitHub
pr-manager, code-review-swarm, issue-tracker, release-manager
SPARC
sparc-coord, sparc-coder, specification, pseudocode, architecture, refinement
Commands
Spawn Agent
npx claude-flow agent spawn --type coder --name my-coderList Agents
npx claude-flow agent list --filter activeAgent Status
npx claude-flow agent status --id agent-123Agent Metrics
npx claude-flow agent metrics --id agent-123Stop Agent
npx claude-flow agent stop --id agent-123Pool Management
npx claude-flow agent pool --size 5 --type coderRouting Codes
| Code | Task | Agents |
|---|---|---|
| 1 | Bug Fix | coordinator, researcher, coder, tester |
| 3 | Feature | coordinator, architect, coder, tester, reviewer |
| 5 | Refactor | coordinator, architect, coder, reviewer |
| 7 | Performance | coordinator, perf-engineer, coder |
| 9 | Security | coordinator, security-architect, auditor |
Best Practices
1. Use hierarchical topology for coordination 2. Keep agent count under 8 for tight coordination 3. Use specialized agents for specific tasks 4. Coordinate via memory, not direct communication
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Use agent-coordination for Ruflo multi-agent orchestration; use single-agent skills when parallel specialist pools add unnecessary overhead.
FAQ
How many agent types does agent-coordination cover?
agent-coordination documents 60+ Ruflo agent types spanning core development, V3 security and performance specialists, and hierarchical, mesh, and adaptive swarm coordinators.
When should agent-coordination be skipped?
agent-coordination should be skipped for single-agent work where no spawning, pool management, or cross-agent coordination is required.
Is Agent Coordination safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.