메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | consumer-slice |
| description | 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. |
| metadata | {"kind":"playbook"} |
Start with docs/consumer-capabilities.md, then read only the API, projection, execution, manifest, and storage docs needed for the capability.
For one capability, state:
.refs/ citations or an explicit bigname divergence in docs/upstream.md.$contract-impact first and keep docs in the same change.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.
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.
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.