メニュー
Hand a release component's claim back to the SRM store, or force-revoke a stuck one. Use when the user says /release-unclaim, release the claim, drop the hold, or revoke <component>.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Recommend the next startable release work from the Swarm Release Manager store — across every release in flight, or within one. Use when the user says /release-next, what is next, what should I work on, or I have a time budget.
Plan a release straight into the shared SRM store: run the structured planning conversation (theme → component sweep → deploy-safety → out-of-scope) and write each confirmed component via component_create — no GitHub issues, no release-plan.json. Use when the user says /srm:release-plan, plan v<X.Y.Z>, plan the next release, scope <release>, or add a component to <release>.
Open a release session against the shared SRM store: confirm the release is seeded, cut the release branch, scaffold the CHANGELOG, open the draft release PR, and optionally (on a yes) link a GitHub milestone. Use when the user says /release-open, start release, cut release branch, or let's start <release>.
Bootstrap a project and release directly in the shared SRM store — born-in-the-store, no GitHub round-trip. Resolve-or-create the workspace project, create the release (theme, version-or-slug, out_of_scope), and offer an optional external-tracker link. Use when the user says /release-init, bootstrap a release in the store, create a project and release in SRM, start a release from scratch, or init a release without a GitHub milestone.
Dispatch parallel work across a release's startable components against the shared SRM store: open a dispatch_run for the wave, then for each member let /srm:release-topic --worktree take the claim and materialize a worktree, and spawn one Claude subagent each that reports progress back to the run. Use when the user says /release-parallel, work on these in parallel, dispatch parallel work, start wave <n>, or run several components concurrently.
Drive the deploy step of a release against the shared SRM store: merge the release PR, watch the deploy, smoke-check production, monitor the window — recording every step on the store's Deploy record so it is resumable across sessions and machines. Use when the user says /release-deploy, deploy the release, ship <release>, or cut over to prod. Deploy-mode only.
| name | release-unclaim |
| description | Hand a release component's claim back to the SRM store, or force-revoke a stuck one. Use when the user says /release-unclaim, release the claim, drop the hold, or revoke <component>. |
Return a claim to the shared SRM store so the component is free for someone else — either gracefully (you hold it) or by force (recovering a stuck/dead hold).
mcp__srm__release_status — see current holds (and the claim ids).mcp__srm__release_claim — gracefully hand back your own claim.mcp__srm__revoke_claim — force a claim off (recovery; any workspace member)./srm:release-status
to find who holds what (each hold carries its claim id).mcp__srm__release_claim { claim }.mcp__srm__revoke_claim { claim }. Confirm with the user first —
revoking pulls the lock out from under whoever held it.release_claim for your own work; reserve revoke_claim for genuine
recovery, and confirm before revoking someone else's hold.mcp__srm__set_component_state { component, state: "merged" }.
Releasing the lock alone leaves the component open, so its dependents stay
blocked until you mark it merged.