/auto-agent
Automatically spawn and manage agents based on task requirements.
> /plugin marketplace add proffesor-for-testing/agentic-qe > /plugin install agentic-qe-fleet@agentic-qe
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/auto-agent
Context preview
What this command does when you run it.
Automatically spawn and manage agents based on task requirements.
Command definition
auto-agent.mdauto agent
Automatically spawn and manage agents based on task requirements.
Usage
npx claude-flow auto agent [options]
Options
- `--task, -t <description>` - Task description for agent analysis
- `--max-agents, -m <number>` - Maximum agents to spawn (default: auto)
- `--min-agents <number>` - Minimum agents required (default: 1)
- `--strategy, -s <type>` - Selection strategy: optimal, minimal, balanced
- `--no-spawn` - Analyze only, don't spawn agents
Examples
Basic auto-spawning
npx claude-flow auto agent --task "Build a REST API with authentication"
Constrained spawning
npx claude-flow auto agent -t "Debug performance issue" --max-agents 3
Analysis only
npx claude-flow auto agent -t "Refactor codebase" --no-spawn
Minimal strategy
npx claude-flow auto agent -t "Fix bug in login" -s minimal
How It Works
1. **Task Analysis**
- Parses task description
- Identifies required skills
- Estimates complexity
- Determines parallelization opportunities
2. **Agent Selection**
- Matches skills to agent types
- Considers task dependencies
- Optimizes for efficiency
- Respects constraints
3. **Topology Selection**
- Chooses optimal swarm structure
- Configures communication patterns
- Sets up coordination rules
- Enables monitoring
4. **Automatic Spawning**
- Creates selected agents
- Assigns specific roles
- Distributes subtasks
- Initiates coordination
Agent Types Selected
- **Architect**: System design, architecture decisions
- **Coder**: Implementation, code generation
- **Tester**: Test creation, quality assurance
- **Analyst**: Performance, optimization
- **Researcher**: Documentation, best practices
- **Coordinator**: Task management, progress tracking
Strategies
Optimal
- Maximum efficiency
- May spawn more agents
- Best for complex tasks
- Highest resource usage
Minimal
- Minimum viable agents
- Conservative approach
- Good for simple tasks
- Lowest resource usage
Balanced
- Middle ground
- Adaptive to complexity
- Default strategy
- Good performance/resource ratio
Integration with Claude Code
// In Claude Code after auto-spawning
mcp__claude-flow__auto_agent {
task: "Build authentication system",
strategy: "balanced",
maxAgents: 6
}See Also
- `agent spawn` - Manual agent creation
- `swarm init` - Initialize swarm manually
- `smart spawn` - Intelligent agent spawning
- `workflow select` - Choose predefined workflows
Read more
auto agent
Automatically spawn and manage agents based on task requirements.
Usage
npx claude-flow auto agent [options]
Options
- `--task, -t <description>` - Task description for agent analysis
- `--max-agents, -m <number>` - Maximum agents to spawn (default: auto)
- `--min-agents <number>` - Minimum agents required (default: 1)
- `--strategy, -s <type>` - Selection strategy: optimal, minimal, balanced
- `--no-spawn` - Analyze only, don't spawn agents
Examples
Basic auto-spawning
npx claude-flow auto agent --task "Build a REST API with authentication"
Constrained spawning
npx claude-flow auto agent -t "Debug performance issue" --max-agents 3
Analysis only
npx claude-flow auto agent -t "Refactor codebase" --no-spawn
Minimal strategy
npx claude-flow auto agent -t "Fix bug in login" -s minimal
How It Works
1. **Task Analysis**
- Parses task description
- Identifies required skills
- Estimates complexity
- Determines parallelization opportunities
2. **Agent Selection**
- Matches skills to agent types
- Considers task dependencies
- Optimizes for efficiency
- Respects constraints
3. **Topology Selection**
- Chooses optimal swarm structure
- Configures communication patterns
- Sets up coordination rules
- Enables monitoring
4. **Automatic Spawning**
- Creates selected agents
- Assigns specific roles
- Distributes subtasks
- Initiates coordination
Agent Types Selected
- **Architect**: System design, architecture decisions
- **Coder**: Implementation, code generation
- **Tester**: Test creation, quality assurance
- **Analyst**: Performance, optimization
- **Researcher**: Documentation, best practices
- **Coordinator**: Task management, progress tracking
Strategies
Optimal
- Maximum efficiency
- May spawn more agents
- Best for complex tasks
- Highest resource usage
Minimal
- Minimum viable agents
- Conservative approach
- Good for simple tasks
- Lowest resource usage
Balanced
- Middle ground
- Adaptive to complexity
- Default strategy
- Good performance/resource ratio
Integration with Claude Code
// In Claude Code after auto-spawning
mcp__claude-flow__auto_agent {
task: "Build authentication system",
strategy: "balanced",
maxAgents: 6
}See Also
- `agent spawn` - Manual agent creation
- `swarm init` - Initialize swarm manually
- `smart spawn` - Intelligent agent spawning
- `workflow select` - Choose predefined workflows
AI-powered quality engineering agents that generate tests, find coverage gaps, detect flaky tests, and learn your codebase patterns — across 11 coding agent platforms.
Repo: proffesor-for-testing/agentic-qe
Other commands on agentic-qe.
- /agent-capabilities
Capability matrix for all agent types
Open command - /agent-coordination
Coordination patterns for multi-agent collaboration.
Open command - /agent-spawning
Guide to spawning agents with Claude Code's Task tool.
Open command - /agent-types
Complete guide to all 87 available agent types in Claude Flow V3
Open command - /health
Show agent health and metrics
Open command - /list
List all active agents
Open command

