菜单
Final mile for a merge-ready Laboratory branch: verify landability, preserve backlog closure, merge through PR or git-native flow, update docs, reflect, and monitor evidence. Trigger: /ship.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Assess and improve codebase readiness for AI coding agents. Dispatches parallel subagents to evaluate style, testing, docs, architecture, CI, observability, security, and dev environment. Produces a scored report with prioritized remediation. Then executes the highest-impact fixes. Use when: "agent readiness", "is this codebase agent-ready", "readiness report", "make this codebase agent-friendly", "agent-ready assessment", "readiness audit", "prepare for agents". Trigger: /agent-readiness, /readiness.
Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check.
Laboratory CI gate audit and verification workflow. Use when checking whether experiment, harness, analysis, docs, or Spellbook harness changes are safe to ship. Trigger: /ci, /gates.
Parallel multi-agent review for Laboratory changes. Prioritizes correctness, scientific validity, provenance, tests, and harness fit. Trigger: /code-review, /review, /critique.
Take one Laboratory backlog item to merge-ready. Composes /shape, /implement, /code-review, /ci, /refactor, and /qa as needed. Stops before merge. Trigger: /deliver.
Capture and share what changed — every app has a demo path; the format depends on the change and the audience. The spectrum runs from a release-notes blurb ("no demo needed, here's what moved") through a curl + JSON paste, a terminal recording, a screenshot, a GIF, up to a polished narrated launch video. Pick the path that fits the change shape (UI / API / CLI / library / agent tool / internal-only), the audience (PR reviewer / team Slack / external customer), and the time budget. Also scaffolds a project-local demo skill for repos with recurring polished-capture needs. Use when: "make a demo", "generate demo", "record walkthrough", "launch video", "PR evidence", "upload screenshots", "demo artifacts", "make a video", "demo this feature", "create a walkthrough", "show what changed", "paste the output", "release notes blurb", "scaffold demo", "generate demo skill". Trigger: /demo.
| name | ship |
| description | Final mile for a merge-ready Laboratory branch: verify landability, preserve backlog closure, merge through PR or git-native flow, update docs, reflect, and monitor evidence. Trigger: /ship. |
| argument-hint | [branch-or-pr] |
Land merge-ready Laboratory work without losing scientific provenance or backlog
closure. /ship assumes /settle already proved the branch clean; if review,
QA, or make ci-smoke has not run for the current HEAD, route back to
/settle.
master or main.make ci-smoke plus review/QA receipts from this session.git status --short, and recent verification
evidence.backlog.d/<id>-*.md items to backlog.d/_done/ on the
shipping branch when the closure is proven.Closes-backlog: trailers in the merge/squash message./reflect for the shipped work and route any new work into backlog or a
follow-up branch./monitor for the relevant signal: CI, experiment artifact integrity,
publication provenance, or Spellbook bridge health.Report: