Can I use this with existing documentation?

Yes, as long as you have a prerequisite REQ-* requirement, this skill will parse that text to identify and number the necessary business rules sequentially.

How does this skill support code autogeneration?

By defining rules with precise regex, formulas, and ranges, the output provides the exact logic an AI needs to generate validation functions and classes without further human clarification.

What is the difference between a Requirement and a Business Rule?

A Requirement (REQ-*) describes a high-level capability (e.g., 'User can log in'), while a Business Rule (BR-*) provides the low-level technical specification (e.g., 'Email must match this specific regex').

What types of rules can this skill extract?

It extracts four primary categories: Validation Rules (format/range), Business Logic (state machines/decisions), Error Handling (templates/messages), and Data Transformation (normalization).

Business Rules Extractor

Name: Business Rules Extractor
Author: foolishimp

byfoolishimp

Productivity & Workflow

Extracts precise, autogenerable business rules from high-level requirements to bridge the gap between documentation and code.

About

The extract-business-rules skill is a specialized tool for the AI SDLC method designed to transform vague requirements (REQ-*) into actionable business rules (BR-*). It systematically identifies validation patterns, state machines, error handling protocols, and data transformation logic. By producing structured, disambiguated specifications, it enables seamless code autogeneration and ensures that every business intent is translated into a testable, independent technical rule. This skill is essential for maintaining a clear audit trail between user needs and implementation details.

Key Features

Maps complex business logic into state machines and decision criteria.
Identifies validation criteria including regex patterns, numerical ranges, and enums.
Outputs structured YAML-style specifications optimized for code generation.
0 GitHub stars
Ensures requirements homeostasis by linking specific BR-* IDs to parent requirements.
Standardizes error handling with consistent templates and user-facing messages.

Use Cases

Translating a signup requirement into specific email regex and password complexity validators.
Establishing standardized error message formats for an entire API suite.
Defining the state transitions and lockout logic for an authentication system.

About

Key Features

Maps complex business logic into state machines and decision criteria.
Identifies validation criteria including regex patterns, numerical ranges, and enums.
Outputs structured YAML-style specifications optimized for code generation.
0 GitHub stars
Ensures requirements homeostasis by linking specific BR-* IDs to parent requirements.
Standardizes error handling with consistent templates and user-facing messages.

Use Cases

Translating a signup requirement into specific email regex and password complexity validators.
Establishing standardized error message formats for an entire API suite.
Defining the state transitions and lockout logic for an authentication system.