Plans
A dependency graph of tasks, run to completion — in parallel where the graph allows — and shipped as one release.
The plan file
A plan names its steps and what each depends on. Steps with no `after` start in parallel; a step launches only once every step it names has merged cleanly; and when every step lands, one final promotion ships all of the plan's work through the repository's release checks.
# plan.yamlname: Ship the reporting modulesteps: - id: schema prompt: Add the reports table. - id: api prompt: Build the reports endpoints. after: [schema] - id: ui prompt: Build the reports page. after: [schema]Run a plan
Creates and starts the plan, following it until it settles. The CLI exits 0 only when the final ship merge is CI-verified.
spaceboy plan run plan.yaml --project prj_...spaceboy plan run plan.yaml --project prj_... --detach # start and returnFollow a plan
Live per-step status: which steps are running, landed, or parked.
spaceboy plan show <planId>Recover a parked plan
A step that parks blocks its dependents and parks the plan. Retry the step with a fresh attempt, or retry a plan parked at its ship phase.
spaceboy plan retry <planId> <stepKey>spaceboy plan retry-ship <planId>