extract-business-rules

Name: extract-business-rules
Availability: InStock
Author: EnigmaWu

Extract and classify business rules from unstructured text documents.

1|Updated Apr 6, 2026

Search Tags:#requirements analysis #classification #text analysis #business rules #user story

Ready to run

npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill extract-business-rules-enigmawu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extract-business-rules
Source: https://github.com/EnigmaWU/MyCodeAgentSkills/tree/main/extract-business-rules
Command: npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill extract-business-rules-enigmawu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps analyze unstructured text, such as vision documents and user stories, to identify and categorize business rules, ensuring clear separation from software implementation.

Core Features & Use Cases

Business Rule Extraction: Identifies and extracts business rules from unstructured text.
Classification: Classifies rules into categories like Facts, Constraints, and Action Enablers.
Use Case: For instance, it can extract the 7% tax rate from a user story as a business rule rather than a functional requirement.

Quick Start

Use the extract-business-rules skill to find the hidden rules in these new user stories.

Frequently Asked Questions about extract-business-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract business rules from unstructured text documents?▼

To extract business rules from unstructured text, you identify statements dictating business behavior and separate them from software implementation details. This process parses vision documents or user stories to isolate distinct functional constraints.

What is the best way to classify extracted business rules during requirements analysis?▼

The best way to classify extracted business rules is mapping them into a predefined taxonomy. This categorizes identified statements into specific groups like Facts, Constraints, and Action Enablers to structure requirements analysis.

Can I separate business rules from functional requirements in user stories?▼

Yes, you can separate business rules from functional requirements in user stories. The extraction process identifies specific business logic, such as a 7% tax rate, and categorizes it distinctly from standard software implementation details.

Does business rule extraction work for legacy code reverse-engineering?▼

Yes, business rule extraction works for legacy code reverse-engineering. It analyzes unstructured text associated with legacy systems to identify and categorize underlying business behavior into a structured taxonomy.

What types of business rules can be identified from unstructured text?▼

Business rules identified from unstructured text include categories like Facts, Constraints, and Action Enablers. This classification ensures clear separation of business logic from functional requirements during analysis.