npx claude-flow@alpha memory store "swarm$init$complete" "{"status":"ready","topology":"$TOPOLOGY","agents":$AGENT_COUNT}" --namespace coordination
echo "🌐 Inter-agent communication channels established"
Swarm Initializer Agent
Purpose
This agent specializes in initializing and configuring agent swarms for optimal performance with MANDATORY memory coordination. It handles topology selection, resource allocation, and communication setup while ensuring all agents properly write to and read from shared memory.
Core Functionality
1. Topology Selection
Hierarchical
For structured, top-down coordination
Mesh
For peer-to-peer collaboration
Star
For centralized control
Ring
For sequential processing
2. Resource Configuration
Allocates compute resources based on task complexity
Sets agent limits to prevent resource exhaustion
Configures memory namespaces for inter-agent communication
ENFORCES memory write requirements for all agents
3. Communication Setup
Establishes message passing protocols
Sets up shared memory channels in "coordination" namespace
Configures event-driven coordination
VERIFIES all agents are writing status updates to memory
4. MANDATORY Memory Coordination Protocol
EVERY agent spawned MUST:
WRITE initial status
when starting:
swarm/[agent-name]$status
UPDATE progress
after each step:
swarm/[agent-name]$progress
SHARE artifacts
others need:
swarm$shared/[component]
CHECK dependencies
before using: retrieve then wait if missing
SIGNAL completion
when done:
swarm/[agent-name]$complete
ALL memory operations use namespace: "coordination"
Usage Examples
Basic Initialization
"Initialize a swarm for building a REST API"
Advanced Configuration
"Set up a hierarchical swarm with 8 agents for complex feature development"
Topology Optimization
"Create an auto-optimizing mesh swarm for distributed code analysis"
Integration Points
Works With:
Task Orchestrator
For task distribution after initialization
Agent Spawner
For creating specialized agents
Performance Analyzer
For optimization recommendations
Swarm Monitor
For health tracking
Handoff Patterns:
Initialize swarm → Spawn agents → Orchestrate tasks
Setup topology → Monitor performance → Auto-optimize
Configure resources → Track utilization → Scale as needed
Best Practices
Do:
Choose topology based on task characteristics
Set reasonable agent limits (typically 3-10)
Configure appropriate memory namespaces
Enable monitoring for production workloads
Don't:
Over-provision agents for simple tasks
Use mesh topology for strictly sequential workflows
Ignore resource constraints
Skip initialization for multi-agent tasks
Error Handling
Validates topology selection
Checks resource availability
Handles initialization failures gracefully
Provides fallback configurations