plan-crew

plan-crew

Show the groundcrew dispatch queue — by default the current repo's plans, or every repo under ~/plans/ on request — and manage it both directions in bulk: promote backlog → todo (add to the queue) and dequeue todo → backlog (pull out). Backed by three plan_keeper_cli.py subcommands: crew queue list (the scoped read), crew queue add (promote → todo), and crew queue drop (dequeue → backlog). Both writers address plans by bare filename within a --repo, so you act on each repo's selections with one call per direction.

Quick reference

• Scope: the current repo by default (crew queue list); --all lists every repo, --repo <name> lists one named repo. See Choosing the scope.
• Reads: ~/plans/<repo>/*.md with frontmatter (one level deep; done/, deferred/ excluded), filtered to the resolved scope.
• Writes: frontmatter Status (and, on promote, Agent when missing, plus a minted Plan-keeper Ticket when absent) — atomic per file.
• Plan-keeper ticket mint: on promote, the plan's Plan-keeper Ticket (plan-<digits>, minted once and frozen) is written if absent, so the dispatch id is visible the moment a plan is queued. Any Linear Ticket / Jira Ticket the plan carries is left untouched (the three ids coexist).
• Dispatch has several gates; the Agent tag is the one this skill manages. groundcrew dispatches a plan only when all of these hold at once:
  1. it lives in a ~/plans/<repo>/ bucket (active — not done//deferred/) whose repo is registered in groundcrew's workspace.knownRepositories;
  2. its Status is todo;
  3. it carries an Agent tag;
  4. it isn't held by an unfinished Blocked-by prerequisite. The Agent gate (3) is the one plan-crew writes — and the one most often missing, because groundcrew skips every agent-less plan in every status, including todo (there is no implicit "default to claude"; an agent-less plan is never dispatched). So crew queue add, which stamps Agent: claude when missing, is what actually makes a plan dispatchable, not merely what makes it visible. The repo-registration gate (1) lives in groundcrew's own config and is outside what plan-crew can set — see ../../groundcrew/README.md.
• Promote is the only automatic Agent writer. crew queue add writes Agent: claude on a plan that has none (a plan that already names an Agent keeps it). Nothing else stamps it: plan-save no longer adds it at birth, plan-do strips it when you start a plan locally, and plan-split leaves its slices agent-less. So the tag's presence means "queued for groundcrew," and nothing adds it behind your back. The flip side: a todo plan can reach this queue agent-less (e.g. a plan-split slice promoted to todo but never queued through here), and such a plan is not dispatchable until you queue it through plan-crew to stamp the Agent.
• Confirmation: required before any mutation.
• Sibling: plan-update is the targeted single-plan frontmatter editor; plan-crew is its multi-select counterpart and the only one that spans repos (with --all). Both can promote a single plan — use plan-update when you already have one specific plan in hand, plan-crew when browsing the queue.