What problem does it solve? When working in a repository that consumes shared DomI policy, it is easy to hand-roll drift checks, misread the pin state, or accidentally vendor DomI-owned logic. This Skill runs the authoritative read-only detector and interprets its verdict so drift status is reported correctly without reimplementing upstream policy. ## Core Features & Use Cases - Drift detection: Runs bin/domi-status.sh against a consumer repo and interprets verdicts including current, behind, forked, unverifiable, malformed, and not-a-domi-consumer. - Category checks: Answers whether a single policy category is inherited via --category <slug>, printing inherited=true|false|malformed for release decisions. - Policy boundary enforcement: Reports and describes the DomI dependency but never vendors, forks, or reimplements DomI-owned policy, and never upgrades unverifiable to current. - Use Case: Before shipping, ask whether your repo's DomI pin is current; the Skill runs the detector, reports behind, and points you to the sanctioned sync-from-domi remediation path instead of a hand-rolled fix. ## Quick Start Ask the agent to check whether this repository's DomI policy pin is current and which policy categories are inherited from upstream.
