Menu
Bless a design doc and begin implementation. Marks the design as accepted, archives superseded docs, updates state files, then starts building.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Go from ignorance to vague familiarity across a whole name-dropping domain — "just deep enough to hurt." The breadth-first sibling to /study: point it at a domain you don't know (often just a name), and it researches the terms worth recognizing, teaches them in batched 1-2-paragraph lessons with a quiz per item, and leaves a durable one-line-each summary you re-skim before the room. Recognition, not reconstruction. Replaces "three hours on Google." Distinct from /study (deep, one system, reconstruct-under-pressure) and /refresh (re-warm what you already learned). Usually user-invoked; agent may suggest it when "make sure I recognize these next time" intent appears.
Assess the current state of a feature, system, or area. Produces a durable assessment doc that downstream skills (/draft, /plan) can consume. Use --capacity to include napkin math (QPS, storage, bandwidth).
Create a working design document for collaborative iteration. Use when scoping a feature, system change, or workflow — the doc is the conversation artifact, not a summary.
Session startup. Walks the .meta/ tree to load user and domain context, orients to the current project, and gives a brief status summary so we can hit the ground running.
Lightweight session start — the sparse floor below /hello. Does a minimal tree walk (signpost-flag inheritance + root WORKFLOW.md) then reads the local .meta/ — but no full state read and no network. Auto-escalates to /hello for domain/neighborhood/full-state context; never runs MCP/API/calendar or hello.check. Use when you want to get moving fast without the full orientation.
Pre-merge review. Diffs the session's work against the base branch, resolves its review dimensions (configurable via signpost `review.dimensions`/`extra-dimensions`, else inferred from the medium — code default: bugs/efficiency/redundancy/architecture — with `redundancy` the recommended-but-configurable example), always runs the structural dimensions (design/track/merge reconciliation), then presents fixes for approval before committing.
| name | ship |
| description | Bless a design doc and begin implementation. Marks the design as accepted, archives superseded docs, updates state files, then starts building. |
The user typed /ship — the design is ready. Mark it accepted, handle
housekeeping, and begin implementation immediately.
State dir convention: Always write to .meta/, creating it (and subdirectories) if needed.
/ship coworking-ux), use thatdesigns/Update the design doc's frontmatter:
---
Status: accepted
Date: <original date>
Accepted: <today>
Assessment: <link, if one exists>
Supersedes: <link, if applicable>
---
If the design has a Likely-supersedes field (from /draft) and the user
didn't object during iteration, treat it as confirmed:
---
Status: superseded
Superseded: <today>
Superseded-by: <new design filename>
---
archive/designs/designs/index.mddesigns/index.md: change status from draft to accepteddecisions.md: one-line summary of what was accepted (create the file if it doesn't exist)in-progress.md: add the work to the Active section (create the file if it doesn't exist)If this design fulfills an item already on roadmap.md (or inbox/todo.md),
graduate it now per the archival convention (references/archival.md):
remove it from its source file and append it to archive/rearview.md with a
Completed: <today> (<branch>) stamp. Match semantically; confirm before
removing a hand-curated item. If nothing matches, skip.
/ship is license to start building immediately. No confirmation step.
Proceed with implementation based on the accepted design.