菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | ssot-entity-list |
| description | 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. |
Use this skill when the request is inventory-shaped: "list all", "show current", "what exists", or "what is missing".
--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.adr list, spec list, feature list, profile list, test list, issue list, claim list, evidence list, risk list, boundary list, release listlist command per requested family instead of mixing manual file scans.$ssot-entity-analyze.$ssot-adr, $ssot-spec, $ssot-feature, $ssot-profile, $ssot-test, $ssot-issue, $ssot-claim, $ssot-evidence, $ssot-risk, $ssot-boundary, $ssot-release).ssot-registry feature list .
ssot-registry test list .
ssot-registry --output-format csv claim list .