菜单
Execute end-to-end release closure from beginning boundary setup through freeze, post-freeze runtime implementation, required-test delivery, verification, publication, and ending boundary verification, with fail-closed gates and mandatory status synchronization.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ssot-e2e-release-closure |
| description | Execute end-to-end release closure from beginning boundary setup through freeze, post-freeze runtime implementation, required-test delivery, verification, publication, and ending boundary verification, with fail-closed gates and mandatory status synchronization. |
Use this skill when the request is boundary-to-boundary release execution, not just partial release commands.
--help during normal SSOT work. Use the command surface and examples in this skill directly.ssot, ssot-registry, ssot-cli, or uv run ssot) and reuse it consistently by substituting that rail into the examples below.feature plan, boundary create|add-feature|add-profile|freezetest list, evidence update, claim evaluate, profile evaluate, evidence verifyregistry sync-statusesrelease create|add-claim|add-evidence|certify|promote|publishvalidate, registry export, graph exportssot validate . --write-report.boundary freeze.test list rows as required verification set.test.kind/test.path.registry sync-statuses --dry-run, review deltas, then apply registry sync-statuses.validate --write-report.claim evaluate, profile evaluate, and evidence verify for boundary scope.release certify --write-report must pass before promotion.release promote must pass before publication.release publish is final progression gate.registry sync-statuses and validate --write-report.boundary freeze straight to verification, proof closure, or release certify; the expected middle is runtime implementation plus real test coverage and evidence.registry sync-statuses as required after evidence updates and after publish.$ssot-e2e-change-orchestrator.uv run ssot validate . --write-report
uv run ssot boundary freeze . --boundary-id bnd:example
# implement frozen runtime code and required tests here
# execute repo-native verification and collect evidence here
uv run ssot registry sync-statuses . --dry-run
uv run ssot registry sync-statuses .
uv run ssot validate . --write-report
uv run ssot release create . --id rel:example --version 0.1.0 --boundary-id bnd:example
uv run ssot release certify . --release-id rel:example --write-report
uv run ssot release promote . --release-id rel:example
uv run ssot release publish . --release-id rel:example
uv run ssot registry sync-statuses .
uv run ssot validate . --write-report
references/boundary-to-boundary-checklist.md../ssot-e2e-change-orchestrator/references/dispatch-policy.mdRoute Codex work onto the SSOT MCP control plane instead of direct SSOT registry edits. Use when a task involves SSOT MCP worker campaigns, maturation slices, leases, conflicts, worker events, campaign state, or MCP-governed registry CRUD and CLI delegation. Choose this skill when the user wants pull-only worker execution, honest claim-tier advancement, or lease-aware implementation and evidence flow.
Execute SSOT MCP pull-worker maturation work targeting T1. Use when Codex should claim leases through SSOT MCP, implement direct runtime behavior, add repeatable project-controlled tests, produce evidence in leased paths, and complete slices honestly without hand-editing the SSOT registry.
Execute SSOT MCP pull-worker maturation work targeting T2 robustness verification. Use when Codex should claim leases through SSOT MCP, harden existing behavior with negative, edge, concurrency, failure, idempotency, compatibility, security, or recovery coverage, and complete slices honestly with distinct T2 evidence.
Execute SSOT MCP pull-worker maturation work targeting T3 certification closure. Use when Codex should claim leases through SSOT MCP, deliver runtime, tests, evidence, and certification-closure work within leased paths, satisfy release, boundary, or profile gates where applicable, and complete slices honestly without direct SSOT registry edits.
Use the latest available `ssot-registry` CLI, either from a current global install or from a repo-local `uv` environment with a repo-local cache, to inspect, validate, and mutate SSOT registries. Use when Codex should operate through the CLI instead of editing `.ssot/registry.json` by hand.
Create, inspect, update, delete, evaluate, verify, link, and unlink claims and evidence, including their feature and test relationships. Use when Codex needs to connect claims to features, tests, and evidence, set claim status, check claim tier, create additive higher-tier claim promotion, or verify whether proof chains are strong enough for release and certification workflows.