boardShow the bd backlog as a status board, or one story by its id. Read-only, any model tier. Use when the user asks to see/list/view their stories, "show the board", or "show story <id>".
milestoneCreate, show, update, or sync the local-only project milestone stored in .milestone.md. Uses a lightweight Socratic loop to clarify the outcome, then tracks done conditions, current epic, bd epic progress, and milestone work not yet represented by an epic. Use when the user asks to set a milestone,
orchestrateAutomate /solve -> review -> land across an ordered set of bd stories and/or epics, with one integration branch and one final GitHub PR or GitLab MR. Frontier model only. Epics expand to their story children; input order controls serial scheduling, --parallel dispatches a ready wave, and --finalize
refineRevise an existing bd story contract by id — typically one labelled needs-refinement after a /solve spec-gap or /validate change-request. Frontier model only; WHAT-only, never code, and returns the story to ready for /solve. Use when the user asks to refine/revise/update a story.
solveImplement one bd story by id in an isolated git worktree+branch at .worktree/<id>, ending at needs-review for /validate. Any tier — matched to the story''s own complexity call. --unattended (passed by /orchestrate when dispatching headless) turns every live question into the spec-gap stop-and-hand-b
specifyAuthor one bd story, or decompose a large goal into an epic. Frontier model only. Authoring only — /board views, /refine revises. Use when the user asks to specify or spec out a problem or goal, open a case, or write a new story or epic.
validateHuman review gate for a needs-review story by id: runs a review pass at effort high via a rung-pinned reviewer subagent that applies fixes in place on bd/<id>, then enacts your verdict — approve (land it on the branch it was forked from, close, unblock dependents), another pass, or a wrong contract