Business Rule Extraction Skill: Turn policy prose into rules a team can actually verify
A product rule hidden in a paragraph is hard to test and easy to interpret differently. The work is to find the decision, not to make the paragraph prettier.
Why this Skill is needed
Business Rule Extraction identifies explicit and implied conditions, actors, outcomes, exceptions, and state changes from policies, requirements, examples, and operational notes.
What the Skill does
The Business Rule Extraction Skill is useful when a team needs a structured review of actor, trigger, condition, decision, exception, state, priority, and source.
Awesome QA Skills organizes Skills by language and testing stage. The series overview explains the shared installation model; this guide stays with Business Rule Extraction.
A practical standard for this Skill is simple: A strong extraction keeps the rule close to its source and distinguishes “must,” “may,” and “usually.” Those words decide whether a test is a violation, a choice, or merely an observation.
Use it when the team needs a repeatable review of actor, trigger, condition, decision, exception, state, priority, and source—especially when several evidence sources disagree or a handoff must explain what remains unverified.
What it does not do
The Business Rule Extraction Skill can organize material, evidence, and next actions for Rule statement. It does not replace:
- Confirmation of rules, scope, and risk by the accountable domain owner.
- A real environment, account, dataset, log, or run record; static analysis does not become runtime evidence by itself.
- Authorization for release, compliance, production actions, or residual-risk acceptance.
- A Human decision when supplied sources conflict.
What it checks
The value of this Skill is not another keyword list. It connects each focus area to an observable input, a judgment, and a way to close the loop. Start with a small matrix based on the source Skill’s output contract:
| Focus | Question before analysis | Handoff output |
|---|---|---|
| Rule statement | Actor, condition, action, result, and exception | Source reference |
| Conflict or gap | Different definitions or missing decision | Owner and question |
| Verification hook | Data, state, or example needed to test it | Next action |
If a row has only a conventional expectation and no source or validation method, keep it open instead of turning it into a pass.
Audit inputs before you start
Before analyzing Rule statement, classify the input into six evidence states. A gap is not automatically a failure, but it must not disappear inside the conclusion.
| State | Meaning | How this Skill should handle it |
|---|---|---|
| known | Directly supported by the supplied material | Keep the source, version, and time with the judgment |
| missing | Needed for this pass but not supplied | Name the smallest evidence action and limit the conclusion |
| conflicting | Sources disagree | Show both sources and route the conflict to an owner |
| stale | Present but outside the relevant version or time window | Mark freshness; old evidence is not current proof |
| out_of_scope | Related but excluded from this pass | Keep the boundary explicit |
| assumptions | Temporarily adopted to continue analysis | State how and when the assumption will be checked |
Keep the input version, scope, environment, evidence locations, and accountable owner together. Without a run record, deliver analysis, design, or a validation plan—not an execution pass.
From problem to structured Finding
Connect the source, scope, evidence state, analysis, owner, action, close condition, and validation before writing the conclusion. The case below keeps this Skill’s identifier and domain context.
Keep the decision layers separate
For Rule statement, do not compress four different kinds of language into “recommended to pass”:
| Layer | How to write it | Application here |
|---|---|---|
| Fact | What the supplied material directly shows | Cite the source, version, input, or run record for the focus |
| Evidence-backed Inference | What several facts support together | Show the inference chain and retain uncertainty |
| Recommendation | The smallest next action | Name the evidence, review, execution, or regression path |
| Human Decision | What an accountable person must decide | Leave scope, risk acceptance, resources, and release meaning to the owner |
A complete case
This case follows Input, Analysis, Finding, Decision, and Validation. When material is incomplete, keep missing, conflicting, or assumptions visible instead of turning them into a pass.
Input
| Material | What to provide | What to do when it is missing |
|---|---|---|
| Business material | Policy, requirement, examples, tickets, and owner | Separate authoritative from illustrative text |
| Terminology | Customer, order, payment, date, status, and exception definitions | Keep conflicting definitions visible |
| Decision need | Test design, implementation clarification, or audit | Do not extract more detail than the decision needs |
Use a request like this:
Use the business-rule-extraction Skill.
Task: extract refund eligibility rules from a support policy, payment guide, and five historical tickets
Inputs: [requirements, versions, links, logs, reports, or data paths]
Scope: [included and excluded objects]
Unknowns: [missing environment, accounts, data, or permissions]
Expected output: [risk-ordered findings, evidence status, and next actions]
Audit the inputs first. Separate facts, assumptions, and open questions. Do not claim execution without a run record.Analysis
Start with a bounded pass—extract refund eligibility rules from a support policy, payment guide, and five historical tickets. Turn “customers can request a refund within 30 days except for used vouchers” into separate rules for actor, time window, voucher state, and outcome. Then flag whether “used” means redeemed, partially redeemed, or order completed.
The handoff should preserve the input version, time window, evidence index, owner, and next validation action. The Skill can organize uncertainty; it cannot manufacture the missing artifact.
Finding
Example finding: turn one problem into a handoff
The field example below shows the recording pattern; it is not an execution result.
If the supplied material cannot prove that Rule statement meets its contract, write the finding like this. It does not invent the missing rule or turn missing evidence into a failure.
| Field | Example wording |
|---|---|
| Source and scope | Record the requirement, version, environment, and the concrete object for Rule statement |
| Finding | The condition or result for Rule statement is not yet traceable to evidence |
| Evidence state | missing / assumptions; use conflicting when sources disagree |
| Impact and priority | Name the affected user, journey, or delivery decision without inflating severity |
| Owner and Human decision | Ask the product, engineering, security, or test owner to confirm the rule and trade-off |
| Action and close condition | Add the smallest missing evidence; close only when source, judgment, and owner can be reviewed |
| Validation | Name one repeatable check, query, or run and retain the raw artifact |
The point is to let the next person walk from the finding back to the source and run an action that can change the decision.
Decision
The accountable owner confirms the decision question and risk trade-off; the Skill does not make that choice.
Validation
Before closing the finding, run the stated validation and retain the raw artifact. Without an execution record, the status remains unverified.
How a Finding enters the next stage
Handoff output
| Output field | Why it exists | Example status |
|---|---|---|
| Rule statement | Actor, condition, action, result, and exception | Source reference |
| Conflict or gap | Different definitions or missing decision | Owner and question |
| Verification hook | Data, state, or example needed to test it | Next action |
Do not write “passed” without a run record, query result, or source artifact. A strong extraction keeps the rule close to its source and distinguishes “must,” “may,” and “usually.” Those words decide whether a test is a violation, a choice, or merely an observation.
Next-stage route
At minimum, hand off the source, evidence state, owner, close condition, and validation action; the next-stage conclusion remains bounded by the evidence state.
How to prepare better input
If the first request contains only a one-line goal, keep the output limited. Add the source version, affected objects, environment, known defects, and decision owner to move from a plausible checklist to a useful review.
A richer input changes the answer here because actor, trigger, condition, decision, exception, state, priority, and source must be tied to evidence rather than inferred from a familiar pattern.
Working with other Skills
- Requirements Analysis:organizes the wider requirement context.
- Requirement Ambiguity Analysis:tests whether rule wording admits multiple readings.
- Decision Table Testing:turns extracted rules into combinations.
Common traps
- Copying policy wording without exposing conditions.
- Treating historical behavior as a rule.
- Merging exceptions into one vague “special case.”
Install and invoke
Install the individual Skill. The series overview carries the longer installation explanation.
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/business-rule-extraction -gAfter installation, invoke it with the business-rule-extraction Skill and attach the real project material.
FAQ
Can extraction resolve conflicting policies?
It can expose the conflict and its impact; the policy owner must decide which rule wins.
Should examples become rules?
Only when the source says they are normative; otherwise keep them as evidence or illustration.
The example above is a design and review pattern, not an execution result. Keep static analysis, runtime evidence, human approval, and release acceptance separate.
References
Source Skill and execution contract
The complete execution contract lives in the Business Rule Extraction prompt. Read it before invoking the Skill; the prompt defines the detailed workflow and output contract. The source directory contains the entry point and supporting assets where they exist.
The entry point centers actor, trigger, condition, decision, exception, state, priority, and source. Keep its decision boundary visible and do not turn a static design into an execution claim.
Reference links
-
Business Rule Extraction prompt:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/business-rule-extraction/prompts/business-rule-extraction.md
-
Awesome QA Skills: Business Rule Extraction source:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/business-rule-extraction
-
Awesome QA Skills GitHub:https://github.com/naodeng/awesome-qa-skills
-
Business Rule Extraction details:https://inaodeng.com/en/qaskills/business-rule-extraction/