Business Process Modeling Skill

Use When

modelling as-is and to-be workflows, actors, handoffs, controls, events, and exceptions to expose requirements; use service-blueprint-requirements for frontstage/backstage service delivery.
Use this procedure when the required source artefacts are available and Business process models and requirement implications is the next lifecycle deliverable.

Use service-blueprint-requirements 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
Process scope, stakeholders, policies, observed evidence, events, and pain points	Process owners, operators, and elicitation records	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.