菜单
Classify a bigname request or diff before coding. Use whenever work may affect public API semantics, coverage or exhaustiveness, shared IDs or enums, manifests, migrations, work ownership, `crates/domain`, replay behavior, upstream citations, or consumer replacement/parity.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
User-invoked only bigname verification loop. Use only when the user explicitly invokes `$verify-loop` or asks to run the verify loop after Codex has implemented work; it spawns `verification_reviewer`, triages findings, confirms real issues with failing tests or checks, fixes them, and repeats until the reviewer is clean or all findings are rejected.
Scope or implement one end-to-end bigname consumer capability. Use when work maps a first-party or public capability to routes, projections, execution behavior, manifests, tests, rollout criteria, or any parity/replacement claim.
Plan or review bigname manifest authority, source-family admission, discovery edges, capability flags, proxy tracking, start-block provenance, watch-plan effects, or manifest-driven invalidation behavior.
Review bigname raw facts, normalized events, canonicality, projection rebuilds, reorg repair, invalidation, execution artifacts, migrations, and storage-family write ownership.
Gather pinned `.refs/` evidence for ENSv1, ENSv2, Basenames, admitted app metadata, reference-indexer comparisons, or reference execution-client comparisons. Use when docs, manifests, tests, comments, or task output make upstream behavior claims or when a change may introduce a divergence.
| name | contract-impact |
| description | Classify a bigname request or diff before coding. Use whenever work may affect public API semantics, coverage or exhaustiveness, shared IDs or enums, manifests, migrations, work ownership, `crates/domain`, replay behavior, upstream citations, or consumer replacement/parity. |
| metadata | {"kind":"playbook"} |
Decide whether the work is implementation-only, doc-first semantic, shared-interface, manifest/admission, storage/replay, or upstream-citation work.
docs/api-v1.md, docs/api-v1-routes.md, docs/consumer-capabilities.mddocs/adrs/0002-surface-resource-identity.mddocs/storage.md, docs/projections.md, docs/execution.mddocs/manifests.mdAGENTS.md § Upstream anchors, .refs/MANIFEST.toml, docs/upstream.mddocs/internal/workstreams.mdProduce a short note:
class: one of implementation-only, doc-first semantic, shared-interface, manifest/admission, storage/replay, upstream-citationdocs_or_artifacts: exact docs, OpenAPI, fixtures, manifests, or migrations that must move with the changeowner: owning boundary or directoryblockers: unresolved semantic questions or required upstream citationscommunication: confirm changed docs, comments, and writeups introduce no undefined project-specific term — link docs/glossary.md on first use instead of re-defining, add necessary new coinages there in the same change, and qualify bare "promotion"/"profile" in prose; wire field names and enum values are contract, not prose (AGENTS.md § Communication).refs/ citations; unsupported claims must not be written.