team-coordination

# Team Coordination

Duyetbot's capability to spawn and coordinate other agents for parallel execution.

## Available Agents

From **@team-agents** plugin:

| Agent | Model | Use For |
|-------|-------|---------|
| `leader` | opus | Complex decomposition, team coordination |
| `senior-engineer` | sonnet | Architectural decisions, complex impl |
| `junior-engineer` | haiku | Clear specs, fast execution |

## When to Spawn

### Spawn @leader
- Multi-component features
- Unclear requirements needing decomposition
- Work requiring architectural decisions

### Spawn @senior-engineer
- Complex implementation logic
- Architectural decisions
- Performance-critical code
- Security-sensitive work

### Spawn @junior-engineer
- Well-defined tasks with clear specs
- Straightforward CRUD operations
- Test writing with clear patterns
- Documentation updates

### Stay Solo
- Single-file changes
- Debugging sessions
- Analysis and investigation
- Quick fixes

## Orchestration Patterns

From **@orchestration** plugin:

### Fan-Out
Launch independent agents simultaneously:
```
├── Agent 1: Task A
├── Agent 2: Task B
└── Agent 3: Task C
→ All run in parallel
```

### Pipeline
Sequential stages:
```
Stage 1 → Stage 2 → Stage 3
(each depends on previous)
```

### Map-Reduce
Distribute then aggregate:
```
Map: Split work across agents
Reduce: Synthesize results
```

### Speculative
Competing approaches:
```
├── Hypothesis A
├── Hypothesis B
└── Hypothesis C
→ Select best evidence-backed
```

## Spawn Protocol

### 1. Task Analysis
```
[ANALYZE] Is this parallelizable?
- Independent components? → Fan-out
- Sequential dependencies? → Pipeline
- Need decomposition? → Spawn @leader
```

### 2. Agent Selection
```
[SELECT] Match agent to task:
- Complex/architectural → @senior-engineer
- Clear/straightforward → @junior-engineer
- Need coordination → @leader
```

### 3. Spawn with Context
```
Task tool with run_in_background=True:

=== WORKER AGENT ===
You are a WORKER spawned by duyetbot.
====