V3 Swarm Coordination
Orchestrate a 15-agent hierarchical mesh to parallelize claude-flow v3 work across security, core, and integration domains while respecting ADRs and a phased timeline.
Overview
V3 Swarm Coordination is an agent skill most often used in Build (also Ship) that orchestrates a 15-agent hierarchical mesh for claude-flow v3 implementation across security, core, and integration domains.
Install
npx skills add https://github.com/ruvnet/ruflo --skill v3-swarm-coordinationWhat is this skill?
- 15-agent hierarchical mesh with queen coordinator and domain-specific worker roles
- Phased execution: security-first (CVE remediation, threat model), then parallel core (memory, integration, performance)
- Task()-driven quick start for swarm init, security architecture, and performance validation
- Aligns implementation to 10 ADRs and a documented 14-week rollout window
- Splits work across security, core, and integration domains with explicit dependency ordering
- 15-agent hierarchical mesh swarm
- 10 ADRs with 14-week timeline framing
- Performance validation targets cited as 2.49x–7.47x
Adoption & trust: 625 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to ship a large multi-domain v3 program but one agent cannot track CVE fixes, memory work, integrations, and performance gates in parallel without dropping dependencies.
Who is it for?
Indie builders running claude-flow or similar multi-agent stacks who are executing a staged v3 roadmap with explicit security gates and parallel specialist roles.
Skip if: Builders patching a single file or a tiny feature where a normal one-agent implementation plan is enough and swarm overhead would add noise.
When should I use this skill?
Implementing claude-flow v3 (or similar) with parallel security, core, and integration work that needs a coordinated multi-agent mesh and phased timeline.
What do I get? / Deliverables
You get a queen-led Task() map with phased security-then-core execution so parallel specialists advance ADR-aligned work on a 14-week-style timeline instead of a single overloaded thread.
- Phased Task() assignment map across security, core, and integration domains
- Coordinator-led execution order aligned to critical security-first gating
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is build/agent-tooling because the skill’s primary job is coordinating parallel agent implementation work, not a one-off launch or ops task. It defines queen-led Task() routing, domain specialists, and mesh topology—classic multi-agent tooling for large product builds.
Where it fits
Initialize the 15-agent mesh and assign queen-coordinated Task() work for v3 feature streams.
Run security-architect and security-auditor tasks for threat models and CVE-1/2/3 remediation before core merge.
Spin integration-architect tasks for deep agentic-flow@alpha wiring while memory and perf agents run in parallel.
Assign performance-engineer tasks to validate 2.49x–7.47x targets after core changes land.
How it compares
Use instead of ad-hoc parallel chats with no coordinator—this is a structured swarm playbook, not a generic project-management MCP.
Common Questions / FAQ
Who is v3 swarm coordination for?
Solo and indie builders using Task()-style multi-agent workflows who are implementing claude-flow v3 (or similar) and need domain-split parallel execution with a clear coordinator.
When should I use v3 swarm coordination?
Use it in Build/agent-tooling when standing up the v3 swarm; in Ship/security when prioritizing CVE remediation and threat modeling; and when validating performance targets before calling the core rollout done.
Is v3 swarm coordination safe to install?
Treat it as operational guidance that may drive broad repo and security changes—review the Security Audits panel on this Prism page and scope Task() permissions before running auditor or remediation agents.
SKILL.md
READMESKILL.md - V3 Swarm Coordination
# V3 Swarm Coordination ## What This Skill Does Orchestrates the complete 15-agent hierarchical mesh swarm for claude-flow v3 implementation, coordinating parallel execution across domains while maintaining dependencies and timeline adherence. ## Quick Start ```bash # Initialize 15-agent v3 swarm Task("Swarm initialization", "Initialize hierarchical mesh for v3 implementation", "v3-queen-coordinator") # Security domain (Phase 1 - Critical priority) Task("Security architecture", "Design v3 threat model and security boundaries", "v3-security-architect") Task("CVE remediation", "Fix CVE-1, CVE-2, CVE-3 vulnerabilities", "security-auditor") Task("Security testing", "Implement TDD security framework", "test-architect") # Core domain (Phase 2 - Parallel execution) Task("Memory unification", "Implement AgentDB 150x improvement", "v3-memory-specialist") Task("Integration architecture", "Deep agentic-flow@alpha integration", "v3-integration-architect") Task("Performance validation", "Validate 2.49x-7.47x targets", "v3-performance-engineer") ``` ## 15-Agent Swarm Architecture ### Hierarchical Mesh Topology ``` 👑 QUEEN COORDINATOR (Agent #1) │ ┌────────────────────┼────────────────────┐ │ │ │ 🛡️ SECURITY 🧠 CORE 🔗 INTEGRATION (Agents #2-4) (Agents #5-9) (Agents #10-12) │ │ │ └────────────────────┼────────────────────┘ │ ┌────────────────────┼────────────────────┐ │ │ │ 🧪 QUALITY ⚡ PERFORMANCE 🚀 DEPLOYMENT (Agent #13) (Agent #14) (Agent #15) ``` ### Agent Roster | ID | Agent | Domain | Phase | Responsibility | |----|-------|--------|-------|----------------| | 1 | Queen Coordinator | Orchestration | All | GitHub issues, dependencies, timeline | | 2 | Security Architect | Security | Foundation | Threat modeling, CVE planning | | 3 | Security Implementer | Security | Foundation | CVE fixes, secure patterns | | 4 | Security Tester | Security | Foundation | TDD security testing | | 5 | Core Architect | Core | Systems | DDD architecture, coordination | | 6 | Core Implementer | Core | Systems | Core module implementation | | 7 | Memory Specialist | Core | Systems | AgentDB unification | | 8 | Swarm Specialist | Core | Systems | Unified coordination engine | | 9 | MCP Specialist | Core | Systems | MCP server optimization | | 10 | Integration Architect | Integration | Integration | agentic-flow@alpha deep integration | | 11 | CLI/Hooks Developer | Integration | Integration | CLI modernization | | 12 | Neural/Learning Dev | Integration | Integration | SONA integration | | 13 | TDD Test Engineer | Quality | All | London School TDD | | 14 | Performance Engineer | Performance | Optimization | Benchmarking validation | | 15 | Release Engineer | Deployment | Release | CI/CD and v3.0.0 release | ## Implementation Phases ### Phase 1: Foundation (Week 1-2) **Active Agents**: #1, #2-4, #5-6 ```typescript const phase1 = async () => { // Parallel security and architecture foundation await Promise.all([ // Security domain (critical priority) Task("Security architecture", "Complete threat model and security boundaries", "v3-security-architect"), Task("CVE-1 fix", "Update vulnerable dependencies", "security-implementer"), Task("CVE-2 fix", "Replace weak password hashing", "security-implementer"), Task("CVE-3 fix", "Remove hardcoded credentials", "security-implementer"), Task("Security testing", "TDD London School security framework", "test-architect")