09-business-rules-analysis

name	09-business-rules-analysis
description	Use when capturing and reconciling policies, calculations, eligibility, decisions, constraints, ownership, and effective dates; use requirements-patterns to express the approved behaviour structurally.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

Business Rules Analysis Skill

Use When

• capturing and reconciling policies, calculations, eligibility, decisions, constraints, ownership, and effective dates; use requirements-patterns to express the approved behaviour structurally.
• Use this procedure when the required source artefacts are available and Business rule catalogue and contradiction log is the next lifecycle deliverable.

Do Not Use When

• Use requirements-patterns when that neighbouring route owns the decision or deliverable.
• Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.

Required Inputs

Artefact	Source or provider	Required?	Behaviour when missing
Policies, process evidence, calculations, exceptions, terminology, and rule owners	Policy owners, domain experts, and elicitation evidence	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.

Workflow

1. Inspect the required inputs and log the exact sources, versions, and unresolved assumptions.
2. Apply this skill's existing domain workflow and decision rules to produce .