okhp3-process-gap-analysis

Topics in the source

• okhp3-process-gap-analysis
• Purpose
• When to use this skill
• When NOT to use this skill
• Gap Analysis Framework
• Type 1 — Structural gaps
• Type 2 — Execution gaps
• Type 3 — Exception gaps

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 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 -- 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 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 -- scripts/analyze-gaps.mjs analyses the as-is process for the following gap types: | Pattern | Gap description | |---|---| | Step with no actorroleid | Unowned activity | | No

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