pm-business-rule-corelisted

# PM - Business Rule: Core Operational 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 **High or Medium priority operational rule** to `domain/business_rules.md`. A rule belongs here when: - It governs regular system behavior in a specific domain (matching, pricing, trust, fulfillment, SLA) - It CAN have exceptions or context-dependent variations (unlike Critical invariants) - Violating it degrades quality or fairness but does not cause immediate irreversible damage - It is referenced by feature designs when implementing the business logic If the rule has NO exceptions and violation causes financial/legal harm → use `pm-business-rule-critical`. If it is a compliance, regulatory, or policy rule → use `pm-business-rule-governance`. **When to run:** During `pm-feature-design` when the JIT design reveals business logic that should be centralized. Or standalone when operational rules nee