ssot-registry

Route 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.

Manage claim entities with full CLI coverage, including link management, evaluation, status progression, and tier controls.

Manage ADR entities with full CLI coverage, including create/update/status/supersede/sync and reservation flows. Use for ADR-focused operations that should stay within the ADR surface.

Create, update, delete, reserve, sync, and inspect SSOT ADR and SPEC documents in repository-local `.ssot/adr` and `.ssot/specs` trees. Use when Codex needs to CRUD ADRs or SPECs, reserve numbers, sync document metadata into `.ssot/registry.json`, or connect architectural/spec changes to feature and release work.

Manage boundary entities with full CLI coverage, including scoped feature/profile membership and freeze operations.

Drive the early SSOT workflow from decision through governed scope definition by creating or updating ADRs, SPECs, and target features with explicit document-to-feature mapping. Use when Codex needs to turn a proposed change into repo-local ADRs, specs, feature rows, and planning metadata before boundary freeze.

Orchestrate end-to-end SSOT delivery workflows across ADRs, SPECs, features, boundaries, implementation, migration, proof wiring, release certification, promotion, publication, and closure. Use when a request spans multiple lifecycle phases, asks for decision-to-release or decision-to-closure delivery, or includes phrases like ADR + SPEC + features + boundary + freeze, schema change + migration + tests + link everything, certifiably fully featured, or certifiably fully conformant.

Run a robust, repeatable, and portable SSOT end-to-end workflow from feature creation through target setting, boundary freeze, post-freeze runtime implementation, required-test delivery, proof execution, status synchronization, certification, promotion, publication, and closure verification. Use when the user asks for full-lifecycle execution with CLI-grounded gates and fail-closed controls.

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.

Analyze SSOT entities and their relationships across families using CLI exports and graph-aware views. Use when Codex must explain cross-entity coverage, gaps, dependency chains, or risk/release impact.

Get a single SSOT entity by ID across ADR, SPEC, feature, profile, test, issue, claim, evidence, risk, boundary, and release surfaces. Use when Codex should inspect one entity deeply before mutation, linking, review, or lifecycle decisions.

List SSOT entities by family and filter criteria across ADR, SPEC, feature, profile, test, issue, claim, evidence, risk, boundary, and release. Use when Codex needs inventories, gap scans, or quick state overviews from CLI truth.

Review SSOT entities for correctness, completeness, and readiness by combining get/list inspection with evaluation and verification commands where supported. Use when Codex should judge whether entities are healthy or ready, not just display them.

Manage evidence entities with full CLI coverage, including claim/test linkage and verification operations.

Create, inspect, update, delete, plan, link, unlink, and set lifecycle for SSOT features. Use when Codex needs to manage targetable features, adjust planning horizon or target claim tier, wire dependencies, or retire/replacement-link features through the CLI instead of hand-editing the registry.

Manage feature entities with full CLI coverage, including planning, lifecycle transitions, and dependency/claim/test link management.

Create features, create tests, and link them bidirectionally with their immediate verification edges. Use when Codex needs to add new coverage units end-to-end instead of only wiring pre-existing rows.

Guide SSOT implementation work after scope freeze, including schema changes, code changes, schema version advancement, migration updates, and test coverage aligned with the frozen boundary. Use when Codex needs repo-specific delivery guidance for implementing governed changes in this ssot-registry repository.

Manage issue entities with full CLI coverage, including planning, release-blocking semantics, and close/reopen lifecycle transitions.

Manage profile entities with full CLI coverage, including composition links and profile evaluation/verification.

Drive the SSOT proof and release phase by creating and linking claims, tests, and evidence, then creating releases, certifying them, promoting them, publishing them, and verifying closure outputs. Use when Codex needs to close the proof chain for a frozen boundary after the frozen implementation work already exists and carry it through release completion.

Upgrade a repository to the latest PyPI `ssot-registry`, run the CLI schema migration, validate the migrated SSOT registry, and repair migration blockers such as Windows uv failures, non-canonical JSON, stale document metadata, and out-of-bounds disposition errors.

Manage release entities with full CLI coverage, including claim/evidence membership and certify/promote/publish/revoke progression.

Manage risk entities with full CLI coverage, including linkage and mitigation/acceptance/retirement lifecycle operations.

Drive SSOT target-setting from planned features to a frozen delivery boundary, including profile inclusion, boundary creation, pre-freeze validation, and freeze. Use when Codex needs to take already-defined scope and turn it into an immutable delivery boundary.

Manage SPEC entities with full CLI coverage, including ADR link management, status/supersede flows, sync, and reservation operations.

Manage test entities with full CLI coverage, including feature/claim/evidence linkage and path-focused verification setup.