flotilla

Show the batch ready to ship in one block - every row, whose it is, who accepted it over which revision, what is held back and why, and the gate it will stand on - so the person can answer once.

Report drift between this repository's flotilla profile and the repository as it is now — CI workflows, required jobs, trunk, and test tiers never run green on this machine.

Check this machine and project for flotilla — Python, platform, git, Claude Code version, the session census, the state directory and the project profile.

Stand the fleet down - retire every flotilla session of this project but your own, keep their trees, and name the work left orphaned.

The arrangement every session in a flotilla fleet follows - who you are, how you start, how work moves through the ledger, whose move it is, and what never to do. Use when your system prompt says you hold a flotilla post, when you start as a flotilla session, or before any flotilla ledger move.

Show which command guards are on and which git hooks are installed, install the git hooks the profile asks for (one yes each), or check what the guards would say about a command.

Show who holds the machine for long runs - bookings, the queue, unbooked runs computing, CI on this machine - so a person can see why a run waits.

Set up flotilla in a repository — measure this machine, show what the repository already declares (test commands, CI, releases), take the recommended settings or ask the few questions only a person can answer, run each test tier once, write .flotilla/project.toml, publish it to trunk, and offer to raise the fleet with this session as its orchestrator. Use when someone asks to onboard, set up, configure or initialize flotilla, to prepare a repository for a fleet of Claude Code sessions, or to re-check an existing flotilla profile for drift.

Put background sessions' permission questions to the person one at a time, oldest first - show the question, ask allow once, allow for the session, or deny, and record the answer so the asking session is told at once.

Retire a flotilla session - stop it, release its post, keep its worktree and name the work it leaves orphaned.

Raise flotilla sessions - background Claude Code sessions, each with a post (orchestrator, sender, reviewer, judge, main, minor), a name given at birth and its own home worktree - from a composition such as "-r 1 -M 2" or the profile's default.

Show the fleet's work - who is idle, working, waiting on whom or blocked, whose move each open row is, what deviates from the route, what git shows outside the ledger, and, given hours, what stalled.

Check the fleet once for what needs attention - deviations, dropped balls (a live session holding a move and not working), a move for a post no live session holds, and sessions that stopped twice while holding a move.