okhp3-process-gap-analysislisted

# okhp3-process-gap-analysis **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) ## Purpose Systematically identify gaps, deviations, and exception paths in a captured as-is process. The analysis distinguishes: 1. **Structural gaps** — missing steps, undefined roles, absent inputs or outputs 2. **Execution gaps** — steps performed inconsistently or only by specific individuals 3. **Exception gaps** — failure paths with no documented handling 4. **Compliance gaps** — steps missing required controls or policy references --- ## When to use this skill - You have an `as-is-process.yaml` and want to identify improvement opportunities - User asks where the current process fails, slows down, or creates risk - Preparing the input for `future-state-and-change-strategy` - User needs a root cause analysis of a known process failure ## When NOT to use this skill - No as-is capture exists — run `as-is-process-capture` first - User wants to design the future state immediately — note the gap analysis is needed first, then run `future-state-and-change-strategy` - Do not propose solutions here — record gaps only; solutions belong in the future-state skill --- ## Gap Analysis Framework `scripts/analyze-gaps.mjs` analyses the as-is process for the following gap types: ### Type 1 — Structural gaps | Pattern | Gap description | |---|---| | Step with no `actor_role_id` | Unowned activity | | No start event or end event | M