pm-business-rule-governancelisted

# PM - Business Rule: Compliance / Policy Rule (JIT Helper) ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. - **Review required:** the artifact contains commitments - after drafting, require the user's review before finalizing; do not close decisions autonomously. --- ## What this skill does Adds a single **Compliance or Policy rule** to `domain/business_rules.md` under the Regulatory/Compliance or User/Authorization section. A rule belongs here when: - It stems from a regulatory or legal requirement (GDPR, PSD2, ePrivacy, local tax law) - It governs admin or ops behavior (what support agents can and cannot do) - It defines a data handling policy (retention, deletion, logging, consent) - It enforces a UX behavioral standard required by law or company policy - It may have regional or partner-specific variations If the rule has no exceptions and violation causes financial/legal harm → use `pm-business-rule-critical`. If it is standard operational logic → use `pm-business-rule-core`. **When to run:** When `pm-privacy-requirements` or `pm-domain-analysis` surfaces a regulatory requirement that needs