Agent Coordination
Spawn, pool, and coordinate many specialized Claude-Flow agent types when a task needs parallel reviewers, coders, or swarm coordinators.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-coordinationWhat is this skill?
- Documents 60+ agent types across core dev, security, swarm, consensus, GitHub, and SPARC roles
- CLI workflows: spawn, list with filters, status, metrics, stop, and sized agent pools
- Explicit skip rule: single-agent work with no coordination needed
- Swarm patterns: hierarchical, mesh, adaptive, and collective-intelligence coordinators
Adoption & trust: 682 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Microsoft Foundrymicrosoft/azure-skills
Azure Aimicrosoft/azure-skills
Azure Hosted Copilot Sdkmicrosoft/azure-skills
Lark Eventlarksuite/cli
Running Claude Code Via Litellm Copilotxixu-me/skills
Setup Matt Pocock Skillsmattpocock/skills
Journey fit
Primary fit
Build/agent-tooling is the canonical shelf because the skill documents claude-flow CLI lifecycle commands for 60+ agent archetypes. Agent-tooling matches spawn/list/status/metrics/stop/pool operations rather than application feature code.
Common Questions / FAQ
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.
SKILL.md
READMESKILL.md - Agent Coordination
# 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 ```bash npx claude-flow agent spawn --type coder --name my-coder ``` ### List Agents ```bash npx claude-flow agent list --filter active ``` ### Agent Status ```bash npx claude-flow agent status --id agent-123 ``` ### Agent Metrics ```bash npx claude-flow agent metrics --id agent-123 ``` ### Stop Agent ```bash npx claude-flow agent stop --id agent-123 ``` ### Pool Management ```bash npx claude-flow agent pool --size 5 --type coder ``` ## Routing 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