spacedock-workflows

Use when writing a ship-flow plan for a shaped entity, especially implementation tasks, TDD needs, runtime commands, or scope anchoring. Layer A delegation: superpowers:writing-plans owns plan authoring; ship-flow:test-driven-development owns fallback TDD contracts.

Use when shaping vague, complex, or ambiguous ship-flow requests into a Shape Up pitch, including `/shape`, discussion, or skill-authoring work.

Use when shape finds UI, domain, contract, interface, visual ambiguity, affects_ui, design_required, or no design reference before plan.

Use when ship-flow needs execute-stage implementation from an approved plan, including wave tasks, blocked work, or PR feedback re-entry. Layer A delegation: superpowers:subagent-driven-development owns wave dispatch discipline.

Use when `/ship` should run ship-flow for an entity id or good-enough raw requirement; vague inputs need shape clarification.

Use when verify passed and ship-flow needs review, PR readiness, PR body drafting, or canonical docs sync. Layer A delegation: pr-review-toolkit:review-pr owns PR review persona philosophy.

Use when verifying execute output before ship, including `/verify`, `/ship`, live worktree checks, UI DCs, e2e, reviewer panel, or NIT fixes. Layer A delegation: e2e-pipeline and ship-flow:ui-verify own UI DC verification; reviewer personas own haiku review.

Use when syncing Ship Flow plugin documentation after stage skill, invariant, workflow, shell primitive, or release changes.

Use when adopting ship-flow in a repo after workflow scaffolding exists, or when onboarding needs initial PRODUCT and ROADMAP context.

Use when ship-flow needs UI verify coverage for render fidelity, selectors, design tokens, computed CSS, dimensions, or handoff targets.

Use when ship-design, schema-designer, or intent-match-verifier needs domain registry routing or knowledge-module lookup context.

Use when a clean session must run a project-intake epic's born-sharped children to PRs in dependency order — after /ship-project or shape-confirm instantiated an epic + depends-on children and they must be dispatched wave-by-wave, not one at a time. Triggers: 'run the epic', 'ship-epic', orchestrate children, wave dispatch, depends-on / DAG ordering.

Use when the captain hands a planned tracker project (a Linear project ref — name/URL/id) and wants it instantiated as committed pipeline entities + a wave/parallel plan in one shot, instead of hand-shaping each issue. Fetches + filters the project's issues, builds a cut-project contract, and instantiates an epic + dotted shaped-children with depends-on edges — then STOPS at entities+plan for a clean session to run via /ship-flow:ship-epic. Triggers: 'ship-project', 'intake this project', 'instantiate the Linear project', project-ref + 'set up the pipeline'.

Use when ship-verify needs a reviewer panel fallback, external reviewer, silent failure reviewer, domain expert, or file:line findings lens.

Use when the project MEMORY.md grows past its budget (SessionStart size warning, or captain notices bloat) — measures against the budget, classifies entries against the 6-gate rubric, proposes a prune/consolidate matrix for captain review, and applies after approval.

Use when the captain asks for Science Officer, 科學官, SO, or EM engineering judgment on ship-flow work, risk trade-offs, scope challenge, worker stewardship quality, or a proceed/narrow/return/block/costly_no call.

Use when adjudicating pending success-mode / failure-mode harvest candidates emitted by ship-review Step 4.5 — decide promote/merge/draft/discard per candidate and stamp the ledger. Closes the T1-3 success-mode lifecycle invariant.

Use when verify stage wants an adversarial cross-model second opinion on the execute diff before PR-create. Wraps `codex exec` (OpenAI Codex CLI) with a ship-flow-tuned locked prompt focused on failure classes Claude reviewers historically miss (schema/migration, silent failure, concurrency, regex blind spots). Opt-in only — NOT auto-fired by any pipeline stage.

Use when mining an external workflow/plugin/source tree for ship-flow improvement candidates while preserving hermetic runtime boundaries.

Use when capturing ship-flow todo ideas, rabbit holes, or quick captain notes without starting a full shape cycle.

Use when ship-flow needs runtime detection for test, build, typecheck, lint, dev, or formatter commands across project stacks.

Use when ship-flow plan, execute, or verify needs TDD, test-first discipline, or RED-before-GREEN evidence for code-bearing tasks.