extract-business-rules

Extract business rules by identifying specific validation patterns, constraints, and logic criteria from requirements. Assign each rule a BR-* identifier with a description, specification (regex, range, formula), error message, and dependencies. This enables precise code generation for validators and error handling across forms, APIs, and workflows.

Requirements describe what a system should do at a high level; business rules specify the precise validation logic, constraints, and decision criteria that enforce those requirements. Business rules are granular enough for automated code generation and testing.

Yes. When business rules are specified with regex patterns, range checks, enum constraints, and error messages in BR-* format, they become precise enough to generate validator functions, API contracts, and form validation logic directly.

Business rule extraction covers validation patterns, range checks, enum constraints, state machines, decision logic, and error messaging. Rules apply to form validation, API contracts, workflow decisions, and data transformation requirements.

Extracting business rules disambiguates vague requirements, reduces misinterpretation, enables consistent code generation across projects, and supports rigorous testing. BR-* specifications create a single source of truth for validation and logic.

Each BR-* rule should include description, specification (regex, range, formulas), error message, autogeneration flag, and dependencies on other rules. This structure ensures rules are complete enough for code generation and error handling implementation.