# Okhp3 Sop Work Instructions > Generate Standard Operating Procedures (SOPs) and work instructions from a validated PNS. Use this skill when the user needs to produce a human-readable procedure document from a process narrative; when they ask to write an SOP, create work instructions, generate a procedure, or produce an ISO 9001-compliant process document. The generated SOP follows ISO 9001 §4.4.2 documented information requirements and embeds its own RACI summary — use okhp3-raci-governance-matrix instead only when a standalone, wider-audience RACI document is needed. Produces sop.md and optional work-instructions.md for each role. - Skill: `okhp3/okhp3-sop-work-instructions` (Agent Skill, multi-file: 8 files) - Install (CLI): `npx skillmds@latest add okhp3/okhp3-sop-work-instructions` - Raw SKILL.md: https://api.skillmd.com/api/skills/okhp3/okhp3-sop-work-instructions/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MIT - Author: OKHP3 (https://skillmd.com/u/okhp3) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/okhp3/okhp3-sop-work-instructions --- # okhp3-sop-work-instructions **BP-SKILL: Business Process Agent Skill Suite** · part of [mermaid-diagram-bpmn](https://github.com/OKHP3/mermaid-diagram-bpmn) · OverKill Hill P³ --- ## Purpose 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 `okhp3-process-narrative-authoring` first - User only wants the BPMN diagram: use `okhp3-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`) ### 3. Definitions Terms and acronyms used in the SOP. Include all role names, system names, and business rule terms. ### 4. Responsibilities RACI summary table: one row per activity, columns R/A/C/I. Derived from `pns.roles_and_raci.raci_matrix[]`. ### 5. Procedure Steps Sequential numbered steps derived from `pns.activity_sequence.activities[]`. Each step: - **Step number** and **title** (from `activity.description`) - **Actor** (from `activity.actor_role_id`) - **Action**: one imperative statement per IEEE 29148 - **Input**: what the actor needs before starting - **Output**: what the actor produces - **System**: which system or tool is used - **Decision note** (if activity has a matching `decision_points[]` entry) - **Exception note** (if activity has a matching `exception_paths[]` entry) ### 6. Exception Handling Table of exceptions: `exception_id`, trigger condition, handling procedure, escalation path, owner role. Derived from `pns.exception_paths[]`. ### 7. Business Rules List of governing rules. Each: rule ID, description, source citation. Derived from `pns.business_rules[]`. ### 8. Related Documents References to PIR, PNS, BPMN diagram, RACI matrix, SIPOC table. ### 9. Revision History Table of document changes. From `pns.revision_history[]`. --- ## Work Instructions (Role-Specific) When `work-instructions.md` is requested, generate one section per role: - Header: role name, activities they own - Numbered steps scoped to that role only - Decision points where their judgement is required - Exception paths they own --- ## Generation Workflow `scripts/generate-sop.mjs` reads `pns.yaml` and: 1. Extracts header metadata from PNS frontmatter 2. Generates Purpose from `babok_core_concepts.need` + `process_box.trigger` 3. Generates Scope from `process_box.inputs[]` + `process_box.outputs[]` 4. Builds definitions from all `role_name`, `system_name`, and `business_rules[].description` terms 5. Renders RACI table from `raci_matrix[]` 6. Renders procedure steps from `activity_sequence[]` with decision and exception notes 7. Renders exception table from `exception_paths[]` 8. Renders business rules list from `business_rules[]` 9. Generates revision history from `revision_history[]` --- ## Handoff Instruction Pass `sop.md` and `work-instructions.md` to `okhp3-publication-handoff-packaging` for bundle assembly. --- ## Execution contract Apply this contract on every run so the artifact is trustworthy and reusable: 1. State the input evidence, assumptions, and unresolved questions before drafting. Never invent missing process facts, owners, controls, dates, or approvals. 2. Preserve stable identifiers and source traceability. When transforming an upstream artifact, retain its IDs and cite the source field or section for each derived decision. 3. Produce the declared artifact exactly, including required fields and valid values. Keep unsupported, uncertain, or not-applicable items explicit instead of silently omitting them. 4. Validate the result with the bundled script or fixture when available. Report validation status, warnings, and any manual review still required. 5. Stop and request the missing input when a boundary, approval authority, or safety-critical rule cannot be inferred. A partial artifact with clearly marked open questions is safer than a confident fabrication. If `scripts/generate-sop.mjs` cannot run, assemble both documents by hand using the nine-section structure in `references/sop-structure-rules.md`, and state in the output that automated generation was not run. ## References Load on demand: - `references/sop-structure-rules.md`: ISO 9001 §4.4.2 and §7.5 requirements, SOP heading conventions, and work instruction generation rules ## Scripts - `scripts/generate-sop.mjs`: generates sop.md and work-instructions.md from PNS YAML ## Assets - `assets/fixtures/sop-example.yaml`: canonical SOP metadata fixture for purchase-approval process ## Evaluation and release status No `evals/evals.json` exists for this skill yet, and none of the five root-level `evals/` categories cover SOP output directly. The only current check is the maintainer-facing `tests/validate-skill.test.mjs` against `assets/fixtures/sop-example.yaml`. Evidence status: `not-run` for task quality and skill uplift. Version 0.2.0 (this pass) added the `compatibility` declaration, the script fallback instruction, and a discovery-time boundary clarifying the relationship between this skill's embedded RACI summary and the standalone `okhp3-raci-governance-matrix` document. Classified minor per the versioning table, not patch. No regression suite exists to run before this bump; that limitation is disclosed, not implied away. --- ## About Part of the **BP-SKILL: Business Process Agent Skill Suite**, published in [overkillhill/mermaid-diagram-bpmn](https://github.com/OKHP3/mermaid-diagram-bpmn). MIT License.