Squashed 'vendor/ruvector/' content from commit b64c2172
git-subtree-dir: vendor/ruvector git-subtree-split: b64c21726f2bb37286d9ee36a7869fef60cc6900
This commit is contained in:
28
.claude/commands/agents/agent-spawning.md
Normal file
28
.claude/commands/agents/agent-spawning.md
Normal file
@@ -0,0 +1,28 @@
|
||||
# agent-spawning
|
||||
|
||||
Guide to spawning agents with Claude Code's Task tool.
|
||||
|
||||
## Using Claude Code's Task Tool
|
||||
|
||||
**CRITICAL**: Always use Claude Code's Task tool for actual agent execution:
|
||||
|
||||
```javascript
|
||||
// Spawn ALL agents in ONE message
|
||||
Task("Researcher", "Analyze requirements...", "researcher")
|
||||
Task("Coder", "Implement features...", "coder")
|
||||
Task("Tester", "Create tests...", "tester")
|
||||
```
|
||||
|
||||
## MCP Coordination Setup (Optional)
|
||||
|
||||
MCP tools are ONLY for coordination:
|
||||
```javascript
|
||||
mcp__claude-flow__swarm_init { topology: "mesh" }
|
||||
mcp__claude-flow__agent_spawn { type: "researcher" }
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
1. Always spawn agents concurrently
|
||||
2. Use Task tool for execution
|
||||
3. MCP only for coordination
|
||||
4. Batch all operations
|
||||
Reference in New Issue
Block a user