/fleet, Parallel Coordinator

Use 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.

Orientation

Use when: Running 2+ independent work streams in parallel, tasks with non-overlapping file scopes that can execute simultaneously.

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.

Commands

Command	Behavior
/fleet [direction]	Decompose direction into parallel streams, execute in waves
/fleet [path-to-spec]	Read a spec file, decompose into streams
/fleet continue	Resume from the last fleet session file
/fleet (no args)	Health diagnostic → work queue → execute
/fleet --quick [task1]; [task2]	Lightweight parallel mode for solo devs, 2+ tasks, single wave, governed merge, minimal durable receipt
/fleet --speculative N [direction]	Try N different approaches to the same task in parallel, see Speculative Mode below
/fleet --teams [direction]	Pilot: native task spine when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is set, see Teams Mode (experimental) below

Protocol

Step 1: WAKE UP

1. Read AGENTS.md, then CLAUDE.md if present (project conventions)
2. Check .planning/campaigns/ for active campaigns
3. Check .planning/coordination/claims/ for external claims
4. Determine input mode: directed, spec-driven, continuing, or undirected
5. Load prior session context: if .planning/momentum.json exists, run node .citadel/scripts/momentum-read.cjs and use the active scopes and recurring decisions to inform work queue prioritization. Skip silently if the file is absent or output is empty.