spacedock

Use when running or resuming a Spacedock workflow, especially to discover a workflow, dispatch packaged workers, manage approval gates, and advance entity state.

First-officer feedback-rejection routing — read the `feedback-to` target, track `### Feedback Cycles`, escalate on cycle 3, consult the budget probe, route findings back to the target stage in the worktree (else fresh), re-run the reviewer, re-enter the gate flow. Invoke at the rejection-handling point when a feedback gate recommends REJECTED or the captain rejects at a feedback-to stage.

Claude dispatch failure recovery — Degraded Mode (triggers, effects, the verbatim captain report, the cooperative shutdown sweep), Break-Glass Manual Dispatch (the manual `Agent()` template), and Context Budget Failure/Dead Ensign Handling (the budget-unavailable stderr conditions, the recovery clause, dead-ensign bookkeeping). Read ONLY at its three resident triggers inside `claude-fo-dispatch.md` — a second dispatch failure, `/spacedock bare`, or `Agent`/`SendMessage` unavailable (Degraded Mode); a non-zero or unavailable `spacedock dispatch build` (Break-Glass); or a budget-fail/zombie/dead-ensign replacement dispatch (Context Budget) — never at boot, never on the happy path.

First-officer gate-presentation rendering — the captain-facing gate-review template plus the nine assembly rules for filling it (lede-first/decision-last spine, chosen-direction prose, report citation, reviewer-finding tiers, single recommendation, concrete bounce-back asks, length budget). Invoke at the gate point after the FO has decided a stage must be presented.

LEGACY worker back-channel via TeamCreate — team creation + naming, the registry-desync recovery ladder, and the bounded TeamDelete terminal teardown. Read ONLY when ToolSearch(select:TeamCreate) matches a TeamCreate tool (a runtime that still exposes the native team registry); when it does not match, the FO's normal dispatch contract in claude-fo-dispatch.md provides the same back-channel with no TeamCreate.

First-officer status query/mutate/display surface — the `status` command flag docs, `--set` field docs, canonical captain-facing invocations, the Captain-Facing State Display rendering, and the GitHub-issue-filing approval gate. Invoke at the first ad-hoc status question, `--set` mutation, `--next-id`/`--resolve` lookup, or issue filing.

Execute workflow stage work as a dispatched worker.

This skill should be used when the user asks to "debrief", "record what happened", "session summary", "write a debrief", or wants to capture session activity (commits, task state changes, decisions, issues) into a structured record for the next session.

This skill should be used when the user asks to "commission a workflow", "create a workflow", "design a workflow", "launch a workflow", or wants to interactively design and generate a plain text workflow with stages, entities, and a first-officer agent.

Use when arriving at or returning to a project that already has AI-agent history and you want the lay of the land before doing anything else — "survey this project", "what have we been doing here", "catch me up", "orient me", "where did we leave off", "what's the state of this project", or picking up a brownfield repo with several in-flight agent tracks. Reads existing agent session history (read-only), reports the implicit workflow, the open decisions, and how often you had to step in, then offers to commission a spacedock workflow from it.

This skill should be used when the user asks to "refit a workflow", "upgrade a workflow", "update workflow scaffolding", or wants to bring an existing workflow's scaffolding files up to date with the current Spacedock version.