メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ssot-entity-analyze |
| description | 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. |
Use this skill when the user asks for cross-entity analysis rather than single-row inspection.
--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.<entity> listregistry exportgraph exportvalidate$ssot-e2e-change-orchestrator.ssot-registry graph export . --format json --output .tmp/graph.json
ssot-registry registry export . --format json --output .tmp/registry.json
ssot-registry feature list .
ssot-registry validate . --write-report
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.