fleet

1# /fleet — Parallel Coordinator
2 
3Use for 3+ independent work streams that can run simultaneously in isolated worktrees. Do NOT use for single-file scope, linear work, or when a marshal or skill suffices.
4 
5## Orientation
6 
7**Use when:** Running 2+ independent work streams in parallel — tasks with non-overlapping file scopes that can execute simultaneously.
8 
9**Don't use when:** Work must execute sequentially or accumulate findings across phases (use `/archon`), a single orchestrated session is enough (use `/marshal`), or the task is simple enough for a bare skill.
10 
11## Commands
12 
13| Command | Behavior |
14|---|---|
15| `/fleet [direction]` | Decompose direction into parallel streams, execute in waves |
16| `/fleet [path-to-spec]` | Read a spec file, decompose into streams |
17| `/fleet continue` | Resume from the last fleet session file |
18| `/fleet` (no args) | Health diagnostic → work queue → execute |
19| `/fleet --quick [task1]; [task2]` | Lightweight parallel mode for solo devs — 2+ tasks, single wave, governed merge, minimal durable receipt |
20| `/fleet --speculative N [direction]` | Try N different approaches to the same task in parallel — see Speculative Mode below |
21| `/fleet --teams [direction]` | Pilot: native task spine when `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` is set, see Teams Mode (experimental) below |
22 
23## Protocol
24 
25### Step 1: WAKE UP
26 
271. Read AGENTS.md, then CLAUDE.md if present (project conventions)
282. Check `.planning/campaigns/` for active campaigns
29…