agent coordination
- Repo stars 54,444
- Author repo ruflo
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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
Sections and files
Listed in source order.
sections -> Purpose → Agent Types → Core Development → V3 Specialized → Swarm Coordination → Consensus
terms -> No English key terms available
files/cmd -> coder · reviewer · tester · planner · researcher · security-architect · security-auditor · memory-specialist
body sha256 -> 671a37a5c987
Core Development
coder,reviewer,tester,planner,researcherV3 Specialized
security-architect,security-auditor,memory-specialist,performance-engineerSwarm Coordination
hierarchical-coordinator,mesh-coordinator,adaptive-coordinator,collective-intelligence-coordinatorConsensus
byzantine-coordinator,raft-manager,gossip-coordinator,consensus-builderGitHub
pr-manager,code-review-swarm,issue-tracker,release-manager