Business rules elicitation and analysis techniques. Covers rule types (constraints, derivations, inferences), decision tables, rule templates, and policy documentation. Use when identifying business policies, constraints, calculations, and decision logic during requirements elicitation.
View on GitHubmelodic-software/claude-code-plugins
requirements-elicitation
plugins/requirements-elicitation/skills/business-rules-analysis/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/melodic-software/claude-code-plugins/blob/main/plugins/requirements-elicitation/skills/business-rules-analysis/SKILL.md -a claude-code --skill business-rules-analysisInstallation paths:
.claude/skills/business-rules-analysis/# Business Rules Analysis
Comprehensive framework for eliciting, documenting, and validating business rules during requirements discovery.
## When to Use This Skill
**Keywords:** business rules, policies, constraints, calculations, derivations, inferences, decision tables, decision logic, rule templates, validation rules, authorization rules, computation rules, condition-action, if-then rules
**Use this skill when:**
- Identifying business policies and constraints
- Documenting calculation and derivation rules
- Creating decision tables for complex logic
- Eliciting authorization and validation rules
- Translating policies into requirement statements
- Analyzing rule interactions and conflicts
- Validating rule completeness and consistency
## Business Rule Categories
### Structural Rules (Facts)
Define the nature of things and relationships:
```yaml
structural_rules:
definition: "Rules that define terms, concepts, and their relationships"
types:
terms:
description: "Definitions of business concepts"
example: "A 'Premium Customer' is a customer who has spent more than $10,000 in the last 12 months"
facts:
description: "Assertions about the business domain"
example: "Each Order must have exactly one Customer"
relationships:
description: "How concepts relate to each other"
example: "A Customer may have zero or more Orders"
documentation_template:
term: "{Term} is defined as {definition}"
fact: "{Subject} {verb} {object}"
relationship: "{Entity A} {cardinality} {Entity B}"
```
### Derivation Rules (Computations)
Calculate or derive values from other data:
```yaml
derivation_rules:
definition: "Rules that compute values from other information"
types:
calculations:
description: "Mathematical computations"
example: "Order Total = Sum of (Line Item Quantity × Unit Price)"
aggregations:
description: "Summary calculations across sets"
example: "Monthly Reven