okhp3-as-is-process-capturelisted

# okhp3-as-is-process-capture **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) ## Purpose 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. --- ## When to use this skill - User describes how a process runs today and wants it documented before redesign - You need a baseline artifact before running `process-gap-and-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 ## When NOT to use this skill - No PIR exists — run `process-intake-and-scope` first to establish scope and boundaries - User wants to design a future state only — skip to `future-state-and-change-strategy` - Do not include aspirational or proposed changes in the as-is record --- ## Capture Workflow ### Step 1 — Import and triage Identify the source: natural language description, bullet list, existing SOP document, or flowchart image. Determine if a PIR already exists. If not, run `process-intake-and-scope` first. ### Step 2 — Extract and sequence steps Parse all process steps in the order they occur. Each step must have: - A single imperative action statement (IEEE 29148) - An identified actor or role - Entry criteria (wha