About agent-coordination
A skill for spawning and coordinating agents on complex tasks, aimed at teams that need parallel work. It offers specialized agent types, command-line management, and task-based role routing.
Key features
- 01Spawn, list, and stop agents
- 02Manage agent pools
- 03Offer specialized agent types
- 04Route roles by task
- 05Recommend coordination via memory
Use cases
- 01Split feature development across agents
- 02Coordinate security or performance work
- 03Track agent status and metrics
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ ruvnet/ ruflo --skill agent-coordinationAfter installing, type/agent-coordinationin Claude Code to confirm it loaded.
Details
From the project READMEAgent 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-coder
List Agents
npx claude-flow agent list --filter active
Agent Status
npx claude-flow agent status --id agent-123
Agent Metrics
npx claude-flow agent metrics --id agent-123
Stop Agent
npx claude-flow agent stop --id agent-123
Pool Management
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
- Use hierarchical topology for coordination
- Keep agent count under 8 for tight coordination
- Use specialized agents for specific tasks
- Coordinate via memory, not direct communication