Generate a Standard Operating Procedure (SOP) and role-specific work instructions from a validated PNS. The SOP is the human-readable manifestation of the process — designed for practitioners who execute the process, not analysts who model it.
When to use this skill
PNS quality score ≥ 75 and ready_for_publication: true
User needs a document that practitioners can follow step-by-step
Organisation requires ISO 9001 §4.4.2 documented information
User wants role-specific work instructions for each lane in the RACI
When NOT to use this skill
PNS does not exist or is below quality threshold — complete process-narrative-authoring first
User only wants the BPMN diagram — use visual-process-modeling directly
Do not generate SOPs from incomplete or unvalidated process descriptions
SOP Structure (ISO 9001 §7.5)
1. Header
Document ID, version, date, owner role
Process name and scope
Effective date and review date
Approved by (role, not person name)
2. Purpose and Scope
One paragraph each:
Purpose — what this SOP achieves and why it exists (from pns.process_box.trigger and babok_core_concepts.need)
Scope — what is included and explicitly excluded (from pns.process_box inputs/outputs and scope-statement.md)