swarm-orchestration

# Swarm Orchestration

This skill guides you through orchestrating teams of Claude Code instances working in parallel. By default, you **delegate** coordination to a spawned team-lead, keeping your involvement minimal.

## Two Orchestration Modes

### Delegation Mode (Default, Recommended)

When you run `/swarm-create`, a team-lead is automatically spawned who handles all coordination:

```
You (orchestrator)
  └── /swarm-create "team" → team-lead auto-spawns
  └── /task-create (high-level goals)
  └── /swarm-message team-lead "Brief with requirements..."
  └── [Team-lead handles everything]
        ├── Spawns workers
        ├── Creates detailed tasks
        ├── Monitors progress
        └── Handles consults
  └── /swarm-status (periodic check-ins)
  └── /swarm-cleanup (when done)
```

**Your role:** Set direction, provide high-level goals, monitor progress, answer escalations.

### Direct Mode (`--no-lead`)

If you want full control, use `--no-lead` to coordinate everything yourself:

```bash
/swarm-create "team" "description" --no-lead
```

For direct mode guidance, see the **swarm-team-lead** skill.

## Quick Start: Delegation Mode

```bash
# 1. Create team (team-lead spawns automatically)
/claude-swarm:swarm-create "auth-feature" "Implement user authentication"

# 2. Create high-level tasks (team-lead will break these down)
/claude-swarm:task-create "Backend Auth" "JWT endpoints with login/signup"
/claude-swarm:task-create "Frontend UI" "Login and signup forms"

# 3. Brief team-lead
/claude-swarm:swarm-message team-lead "Please coordinate implementation. Use sonnet for workers. Let me know if you need architectural decisions."

# 4. Monitor progress (periodically)
/claude-swarm:swarm-status auth-feature
/claude-swarm:swarm-inbox

# 5. Cleanup when done
/claude-swarm:swarm-cleanup auth-feature
```

That's it! The team-lead handles spawning workers, assigning tasks, and coordinating execution.

## When to Use Swarms

**Good candidates:**

- **Large features** wi