What problem does it solve? Business rules often get buried inside requirements documents or scattered across source code, making them hard to find, update, and keep consistent when policies or regulations change. This Skill provides a structured method to identify, classify, and catalog business rules as standalone, traceable artifacts. ## Core Features & Use Cases - Rule Classification: Categorize each rule as Fact, Constraint, Action Enabler, Inference, or Computation with a unique ID (e.g., BR-001). - Structured Catalog Template: Capture source, rationale, volatility, effective date, and traceability links to functional requirements and use cases for every rule. - Conflict Detection: Use a rule conflict matrix to identify and resolve contradictions between rules before they reach production. - Use Case: When regulatory rules change annually, maintain them in a separate catalog so you update one rule entry instead of rewriting multiple sections of the SRS. ## Quick Start Ask the agent to document the business rules for your project, classifying each rule by type and tracing it to the related functional requirements.
