Skip to main content
An Overdeck issue moves through plan, work, review, test, ship and merge. These commands drive and inspect that pipeline from a shell; see Review convoy for more on how a change moves through review on its way to merge.

pan plan

Run or inspect an issue’s planning lifecycle: generate the PRD and xBRIEF, then finalize and promote the plan to canonical state.
See Planning for what planning produces and when to skip it.

pan task

Read and update xBRIEF item state for one issue: claim an item, mark it done, or change its lifecycle.
pan task done only records an item once every id passed to it has a commit on the pushed branch carrying the body line Item: <id>; if any id lacks one, nothing is written. See Work through the checklist with pan task.

pan scope

Move an xBRIEF plan’s lifecycle status. Every subcommand rewrites status fields on the spec file in place; none of them moves the file between directories, even though some help text still describes it that way. When the issue’s workspace no longer exists, the change is made on the primary checkout, then committed and pushed.
On every subcommand except list, --project <path> defaults to the project resolved from the issue; pan scope list without it lists every registered project. See Change lifecycle status with pan scope.

pan show

Print a unified view of one issue: derived state, CV (agent work history), context engineering state, and health. With no option it prints a compact summary built from derived issue state, the last few pipeline journal entries, health, and recent CV entries; each option narrows the output to that one view in full detail.

pan staffing

Show the work model and swarm policy currently in effect for an issue. It is read-only: it reads the work model from config.yaml (roles.work) and the swarm policy from config.yaml plus the project’s projects.yaml entry, and takes no override of its own. Pass a one-off model at spawn time instead, with pan start --model.

pan parked

List every issue parked in a stall orbit (an operator gate, a zombie session, an idle but running agent), oldest first, with why each is parked and what would release it.

pan ask

Run by a work agent to ask the operator a blocking decision. It records the question in the issue’s pipeline journal, the dashboard shows it under Needs you, and the operator’s answer arrives as a message in the agent’s own session.

pan answer

Shows a numbered choice menu that is on screen in an agent’s terminal pane, or picks option n from it. pan answer does not answer a pan ask request; the operator answers that from Needs you in the dashboard, not with this command.
The <id> may be an issue id, an agent session name, or a named singleton session. It prints one of three outcomes: the menu, a confirmation that option n was selected, or an error that the menu is gone, the menu changed (run pan answer again), or delivery is unconfirmed (check the terminal).

pan close

Verify an issue’s Definition of Done, clean up its workspace residue, and close the issue on the tracker. It checks eight rows, in order: Review passed, Tests passed, Verification green on the branch, Merged to main, Post-merge lifecycle ran, Verified on main, Version strings propagated, and Deployed. After teardown it records a ninth row, Close-out teardown verified, which no flag overrides.
--abandon and --residue are operator-conversation only, and neither combines with each other or with any --accept-* flag. Both require the tracker issue to be closed already. From inside an agent, only operator conversations (conv-*) and the Flywheel may run pan close, and the Flywheel cannot pass --accept-* flags.

pan strike

Spawn a strike agent that implements a fix on a strike branch and opens a pull request against the base branch. A strike skips planning, the review convoy, test and ship: on GitHub its PR gets one automatic quick review per head, and once that review approves, the merge train merges it ahead of the queue after the 5-minute cancel window. In a project that holds for UAT, it waits for your Merge click.

pan flywheel

Start, stop, pause, resume, or inspect the Flywheel conversation, the loop that drives issues through the pipeline autonomously.
See Use the CLI for how pan flywheel and pan orders work together. See Flywheel for what the loop does and how to read its page.

pan orders

Create and manage Flywheel order books: named, lane-ordered lists of issues a Flywheel run works from.
See Use the CLI.

pan backlog

Manage the backlog sequencer that ranks and pins issue work.
See Flywheel for the Backlog Sequencer page and its passes.

pan merge

Cancel a pending auto-merge.
See Cancelling for what the cooldown window is and what cancelling changes.

pan swarm

Start, dispatch, recover, or inspect parallel swarm slots for a planned issue, when the xBRIEF has independent items that can run at once.
See CLI for the gated dispatch protocol these commands drive.

pan spawn

Create a worker pane for one xBRIEF item, in its own item worktree.

Get help