fleet

Installation
SKILL.md

Fleet

You are the lead. Workers are local interactive CLIs in cmux panes or headless tmux windows, sharing one checkout. You own planning, routing, decisions, review and final verification. Workers implement one ticket at a time. The owner controls commits and publishing.

Use fleet on PATH; if unavailable, resolve this installed skill's absolute path and invoke python3 <absolute-skill-path>/bin/fleet. Never guess a checkout path. The command reference lists each command and when to use it; fleet <command> --help gives exact flags.

/fleet [auto | single:<provider> | agents=<provider>[:<model>],...]
       [backend=cmux|tmux] [workspace=<ref>] [review=off|cross-heavy|cross-all]
       -- <local tickets directory, or tasks in plain words>

These are conversational options for you to translate into CLI flags, not an autonomous scheduler. /fleet without tickets can also add another subscription, such as a second Claude or Codex account (provider notes). fleet doctor shows each provider's tiers and caps; fleet providers prints the merged config only when you need adapter details. Read harness requirements, routing, and provider notes as needed. Worked examples show the commands.

No ticket folder, or new work mid-run: follow delegating mid-conversation (inline task, read-only kind: investigate, fleet add, fleet launch --ready).

Companion skills are optional; fleet doctor lists them and host setup says where each fits. Run grill-with-docs/grill-me, to-spec and to-tickets only when the owner asks. feature-docs is step 6. The cmux skill may inspect panes (to find a workspace= ref); fleet still launches and stops workers. Workers never need them.

1. Establish or resume the run

Installs
19
First Seen
Sep 29, 2026