business-rule-extractor
Skill28 starsChanged 8 months agoMITView on GitHub
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SkillMedev/legacy-modernizationtheir own version, first seen Oct 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- SkillMedev/legacy-modernization★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository105 other files it gives its agents.
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- catwoe-root-definitionSkill
- constraint-detectorSkill
- critical-thinking-bias-checkSkill
- definition-of-done-drafterSkill
- deliverable-consistency-checkSkill
- edge-case-elicitorSkill
- evidence-gap-reviewSkill
- functional-vs-nonfunctional-splitterSkill
- interview-designSkill
- moscow-prioritisationSkill
- observation-study-planSkill
- pestle-analysisSkill
- porters-five-forcesSkill
- power-interest-gridSkill
- probe-question-generatorSkill
- problem-statement-refinerSkill
- process-modelling-and-improvementSkill
- process-model-specSkill
- proto-requirements-normalizerSkill
- prototype-elicitationSkill
- pyramid-funnel-diamond-interviewerSkill
- questionnaire-designSkill
- questionnaire-pilot-checkerSkill
- raci-matrixSkill
- raci-rasci-builderSkill
- requirements-conflict-checkerSkill
- requirements-elicitationSkill
- requirements-gap-auditorSkill
- requirements-interrogatorSkill
- requirements-packagerSkill
- requirements-prioritizerSkill
- requirements-quality-checkSkill
- requirements-traceability-starterSkill
- see-i-clarifierSkill
- ssm-analysisSkill
- stakeholder-analysisSkill
- stakeholder-communication-plannerSkill
- stakeholder-registerSkill
- strategy-analysisSkill
- swot-prioritisationSkill
- to-be-process-designerSkill
- use-case-specificationSkill
- value-proposition-analysisSkill
- workshop-designSkill
- acceptance-criteria-writerSkill
- ambiguity-hunterSkill
- as-is-process-investigatorSkill
- assumption-extractorSkill
- assumptions-constraints-logSkill
- benefit-hypothesis-writerSkill
- breakout-structure-designerSkill
- business-problem-framingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Prefer structured outputs over loose prose.
- Distinctive: line 55
Do not pretend weak evidence is confirmed fact.
- Distinctive: line 56
Do not confuse stakeholder opinion with validated rule or process truth.
- Distinctive: line 57
Do not hide missing coverage behind polished wording.
- Distinctive: line 58
Do not flatten politically different stakeholders into one generic audience.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
business-rule-extractor
Purpose
Extract explicit and implicit business rules from interviews, documents, process descriptions, and system behavior.
Trigger this skill when
- Rules are scattered across documents, people, and legacy behavior.
- Stakeholders speak in examples but the underlying rules are unclear.
- The process depends on approvals, eligibility logic, exceptions, or policy constraints.
Expected inputs
- documents
- interview notes
- process notes
- system descriptions
Deliverables
- business rules register
- rule sources
- rule ambiguities
- rule conflicts
Operating procedure
- Scan source material for decision logic, eligibility criteria, timing rules, approval conditions, thresholds, and exceptions.
- Rewrite each rule into clear conditional language where possible.
- Link each rule to its source and confidence level.
- Separate confirmed rules from inferred rules.
- Flag conflicts, missing parameters, and unclear authority.
Quality gates
- Rules are atomic and testable.
- Source and confidence are captured.
- Inferred rules are clearly marked.
Handoff targets
- as-is-process-investigator
- to-be-process-designer
- requirements packs later
Output style
- Be explicit about uncertainty.
- Prefer structured outputs over loose prose.
- Separate confirmed findings, inferred findings, and open questions.
- Preserve source context where practical.
Failure modes to avoid
- Do not pretend weak evidence is confirmed fact.
- Do not confuse stakeholder opinion with validated rule or process truth.
- Do not hide missing coverage behind polished wording.
- Do not flatten politically different stakeholders into one generic audience.
Minimum output skeleton
## Summary
## Findings
## Structured outputs
## Risks or tensions
## Open questions
## Recommended next skillDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

