business-rule-extraction

What problem does it solve?

Business decisions get duplicated and drift across UI, controllers, SQL, jobs, imports, and tests because rules are implemented in many places without a single authoritative source or shared reasoning.

Core Features & Use Cases

• Extracts and names authoritative rules: identifies the stable rule id, one owner, and one enforcement layer so every entry point applies the same decision.
• Captures reasons, not just booleans: structures outcomes as decision + reason (with evidence) to support customer support and auditability.
• Handles exceptions and precedence explicitly: treats overrides as their own rules, defines precedence when multiple rules apply, and documents effective dating.

Quick Start

Use the business-rule-extraction skill to name and document the eligibility and compliance rules driving a workflow (including overrides, precedence, and effective dates) so the system can answer exactly why an action was allowed or denied.