flight

Use when clearing out branches whose work has already shipped — "clean up the branches", "delete merged branches", "prune old feature branches", "what branches can go", "tidy up the worktrees", "origin is full of old feature branches". Finds feature/bugfix/release/batch branches already merged into a stage, cross-checks each against its issue, previews them, and deletes the local ref, the remote ref, and the leftover worktree only on your go-ahead.

Use when the user invokes `/issue <description>`, or says "file an issue", "open a ticket", "track this", "add an issue for that", "create an issue", "log a bug" — even if the description is terse or vague. Also use when an existing issue's title/body is now stale and needs updating, or a comment should be added. Operates through the flight dispatcher.

Use when advancing the current branch to the next stage — "promote this", "promote to qa", "promote develop to main", "open a PR for this branch", "this branch is ready". Moves the current branch one hop up the configured stages pipeline (e.g. feature → develop → qa → main), applying that hop's merge strategy and gate.

Use when promoting several first-hop feature branches at once — "promote each zone", "promote the first zone", "promote issues 18, 93, 12", "promote all to-test", "batch promote", "ship the batch". Promotes a selected group of feature branches into stages[0], honoring that hop's merge strategy (direct → N merges; pr → one PR per group). For a single branch use promoting-a-branch.

Use when the user invokes `/queue-batches`, `/queue-batches NxM` (e.g. `3x5`), or says "queue up some batches", "kick off parallel work on some issues", "run N groups of M issues in parallel". Dispatches N background agents in isolated git worktrees, each working M issues sequentially through the working-an-issue lifecycle (stopping at the to-test merge gate), with live status streaming and question routing back to the user.

Use when setting up a repo for flight for the first time — "set up this repo", "set up flight", "configure flight", "set up labels", "bootstrap labels", "add the default labels" — when filing/triage reveals the repo has no flight config or few labels, or when retrofitting the backend breadcrumb onto an already-configured repo ("add the flight note/breadcrumb", "add it to AGENTS.md"). Writes the flight config + secrets (backend coordinates, stage pipeline, worker model), reconciles a default label taxonomy against existing labels (creating only what's missing, after a preview), and leaves a backend breadcrumb in the repo's agent instructions (AGENTS.md, imported by CLAUDE.md).

Use when the user asks what to work on next — "what should I work on", "what's next", "any quick wins", "show me the open issues", "what's in the backlog", "pick something to do". Lists and filters open issues for selection. Read-only — it never creates or modifies anything.

Use when starting, progressing, or finishing work on a specific issue — "let's work on