okhp3-as-is-process-capture

Topics in the source

• okhp3-as-is-process-capture
• Purpose
• When to use this skill
• When NOT to use this skill
• Capture Workflow
• Step 1: Import and triage
• Step 2: Extract and sequence steps
• Step 3: Assign stable IDs

BP-SKILL: Business Process Agent Skill Suite · part of mermaid-diagram-bpmn · OverKill Hill P³ -- Capture and normalise the current-state (as-is) process into a structured YAML artifact. The as-is record uses stable act-NNN step identifiers that persist across revisions, making gap analysis and change tracking tractable. -- User describes how a process runs today and wants it documented before redesign You need a baseline artifact before running okhp3-process-gap-exception-analysis PIR exists but steps lack stable IDs: normalise them with scripts/assign-step-ids.mjs User imports existing process notes, SOPs, or procedure documents for structuring No PIR exists: run okhp3-process-intake-and-scope first to establish scope and boundaries User wants to design a future state only: skip to okhp3-future-state-change-strategy Do not include aspirational or proposed changes in the as-is record -- Identify the source: natural language description, bullet list, existing SOP document, or flowchart image. Determine if a PIR already exists. If not, run okhp3-process-intake-and-scope first. Parse all process steps in the order they occur. Each step must have: A single imperative action statement

This is an excerpt. Refer to the complete source and its current requirements.