What problem does it solve? Teams with layered governance rules (org, domain, service, repo) struggle to know which rules actually apply to a given feature scope, and whether a feature satisfies them before promotion. This Skill resolves the effective ruleset through additive inheritance and checks feature artifacts against it. ## Core Features & Use Cases - Rule Resolution: Merges constitution files across org → domain → service → repo levels using field-specific strategies (intersection for permitted tracks, union for required artifacts, strongest-wins for gate modes). - Compliance Checking: Validates a feature's track and required artifacts against the resolved constitution, returning PASS/FAIL per check with hard vs informational gate severity. - Progressive Display: Returns only the rules relevant to the current phase and track so feature authors are not overwhelmed by irrelevant governance requirements. - Use Case: Before promoting a feature from planning to dev, run a compliance check to confirm the business-plan and tech-plan artifacts exist and the chosen track is permitted at every governance level. ## Quick Start Ask the assistant to resolve the governance rules for domain platform and service auth using the configured governance repo, then check my feature's compliance for the planning phase.
