Added in git-flow
This commit is contained in:
@@ -0,0 +1,62 @@
|
||||
# Automatic Topology Selection
|
||||
|
||||
## Purpose
|
||||
Automatically select the optimal swarm topology based on task complexity analysis.
|
||||
|
||||
## How It Works
|
||||
|
||||
### 1. Task Analysis
|
||||
The system analyzes your task description to determine:
|
||||
- Complexity level (simple/medium/complex)
|
||||
- Required agent types
|
||||
- Estimated duration
|
||||
- Resource requirements
|
||||
|
||||
### 2. Topology Selection
|
||||
Based on analysis, it selects:
|
||||
- **Star**: For simple, centralized tasks
|
||||
- **Mesh**: For medium complexity with flexibility needs
|
||||
- **Hierarchical**: For complex tasks requiring structure
|
||||
- **Ring**: For sequential processing workflows
|
||||
|
||||
### 3. Example Usage
|
||||
|
||||
**Simple Task:**
|
||||
```
|
||||
Tool: mcp__claude-flow__task_orchestrate
|
||||
Parameters: {"task": "Fix typo in README.md"}
|
||||
Result: Automatically uses star topology with single agent
|
||||
```
|
||||
|
||||
**Complex Task:**
|
||||
```
|
||||
Tool: mcp__claude-flow__task_orchestrate
|
||||
Parameters: {"task": "Refactor authentication system with JWT, add tests, update documentation"}
|
||||
Result: Automatically uses hierarchical topology with architect, coder, and tester agents
|
||||
```
|
||||
|
||||
## Benefits
|
||||
- 🎯 Optimal performance for each task type
|
||||
- 🤖 Automatic agent assignment
|
||||
- ⚡ Reduced setup time
|
||||
- 📊 Better resource utilization
|
||||
|
||||
## Hook Configuration
|
||||
The pre-task hook automatically handles topology selection:
|
||||
```json
|
||||
{
|
||||
"command": "npx claude-flow hook pre-task --optimize-topology"
|
||||
}
|
||||
```
|
||||
|
||||
## Direct Optimization
|
||||
```
|
||||
Tool: mcp__claude-flow__topology_optimize
|
||||
Parameters: {"swarmId": "current"}
|
||||
```
|
||||
|
||||
## CLI Usage
|
||||
```bash
|
||||
# Auto-optimize topology via CLI
|
||||
npx claude-flow optimize topology
|
||||
```
|
||||
@@ -0,0 +1,50 @@
|
||||
# Parallel Task Execution
|
||||
|
||||
## Purpose
|
||||
Execute independent subtasks in parallel for maximum efficiency.
|
||||
|
||||
## Coordination Strategy
|
||||
|
||||
### 1. Task Decomposition
|
||||
```
|
||||
Tool: mcp__claude-flow__task_orchestrate
|
||||
Parameters: {
|
||||
"task": "Build complete REST API with auth, CRUD operations, and tests",
|
||||
"strategy": "parallel",
|
||||
"maxAgents": 8
|
||||
}
|
||||
```
|
||||
|
||||
### 2. Parallel Workflows
|
||||
The system automatically:
|
||||
- Identifies independent components
|
||||
- Assigns specialized agents
|
||||
- Executes in parallel where possible
|
||||
- Synchronizes at dependency points
|
||||
|
||||
### 3. Example Breakdown
|
||||
For the REST API task:
|
||||
- **Agent 1 (Architect)**: Design API structure
|
||||
- **Agent 2-3 (Coders)**: Implement auth & CRUD in parallel
|
||||
- **Agent 4 (Tester)**: Write tests as features complete
|
||||
- **Agent 5 (Documenter)**: Update docs continuously
|
||||
|
||||
## CLI Usage
|
||||
```bash
|
||||
# Execute parallel tasks via CLI
|
||||
npx claude-flow parallel "Build REST API" --max-agents 8
|
||||
```
|
||||
|
||||
## Performance Gains
|
||||
- 🚀 2.8-4.4x faster execution
|
||||
- 💪 Optimal CPU utilization
|
||||
- 🔄 Automatic load balancing
|
||||
- 📈 Linear scalability with agents
|
||||
|
||||
## Monitoring
|
||||
```
|
||||
Tool: mcp__claude-flow__swarm_monitor
|
||||
Parameters: {"interval": 1000, "swarmId": "current"}
|
||||
```
|
||||
|
||||
Watch real-time parallel execution progress!
|
||||
Reference in New Issue
Block a user