Requirements Patterns Skill

Use When

expressing complex behaviour with decision tables, state transitions, CRUD matrices, or requirement patterns; use business-rules-analysis to establish the policy content first.
Use this procedure when the required source artefacts are available and Pattern-based requirement models is the next lifecycle deliverable.

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

Artefact	Source or provider	Required?	Behaviour when missing
Analysed requirements, rules, states, actors, data concepts, and exceptions	Requirements analysis and domain owners	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.