okhp3-process-gap-analysis
Skill3 starsChanged 2 months agoMITView on GitHub
Identify deviations, gaps, and exception paths between an as-is process capture and its intended design. Use this skill when the user wants to find where a process breaks down, where steps are missing or inconsistent, where exception handling is undefined, or where current execution differs from documented procedure. Use when they say "what's wrong with the current process", "find the gaps", "where does this break", or "analyze exceptions". Produces a gap analysis report and exception catalog.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decision-recordsSkill
- catalog-integritySkill
- frontend-designSkill
- okhp3-artifact-validationSkill
- okhp3-as-is-process-captureSkill
- okhp3-brand-style-registrySkill
- okhp3-capture-intakeSkill
- okhp3-chatgpt-project-migrationSkill
- okhp3-custom-gpt-builderSkill
- okhp3-custom-gpt-readinessSkill
- okhp3-decision-model-authoringSkill
- okhp3-elicitation-interviewsSkill
- okhp3-equilibrium-reviewSkill
- okhp3-evidence-standardSkill
- okhp3-future-state-strategySkill
- okhp3-gpt-skill-conversion-planSkill
- okhp3-graduation-gateSkill
- okhp3-handoff-packagingSkill
- okhp3-notion-capture-routerSkill
- okhp3-outcome-modeling-coreSkill
- okhp3-overkill-hill-brandSkill
- okhp3-process-captureSkill
- okhp3-process-intake-and-scopeSkill
- okhp3-project-promotionSkill
- okhp3-replit-build-in-publicSkill
- okhp3-replit-canvas-boardSkill
- okhp3-replit-design-pipelineSkill
- okhp3-replit-free-mode-autonomySkill
- okhp3-replit-github-syncSkill
- okhp3-replit-multi-artifactSkill
- okhp3-replit-repl-janitorSkill
- okhp3-replit-repository-janitorSkill
- okhp3-replit-task-executorSkill
- okhp3-repository-janitorSkill
- okhp3-repository-organizerSkill
- okhp3-session-handoffSkill
- okhp3-skill-catalogerSkill
- okhp3-skill-discoverySkill
- okhp3-skill-foundrySkill
- okhp3-source-backed-researchSkill
- okhp3-thread-context-extractionSkill
- okhp3-thread-extract-chatgptSkill
- okhp3-thread-extract-claudeSkill
- okhp3-triage-and-fileSkill
- okhp3-vite-github-pagesSkill
- production-build-verificationSkill
- published-keyboard-recovery-checkSkill
- publish-health-checkSkill
- publishing-trigger-checkSkill
- static-route-validationSkill
- validation-smokeSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- okhp3-skill-promotionSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 63
No as-is capture exists — run as-is-process-capture first
- Distinctive: line 65
Do not propose solutions here — record gaps only.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
okhp3-process-gap-analysis
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Purpose
Systematically identify gaps, deviations, and exception paths in a captured as-is process. The analysis distinguishes:
- Structural gaps — missing steps, undefined roles, absent inputs or outputs
- Execution gaps — steps performed inconsistently or only by specific individuals
- Exception gaps — failure paths with no documented handling
- Compliance gaps — steps missing required controls or policy references
When to use this skill
- You have an
as-is-process.yamland 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-capturefirst - 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 | Missing process boundary |
Input with no source | Untraced input |
Output with no consumer | Undelivered output |
business_rules empty | Undocumented constraints |
Type 2 — Execution gaps
| Pattern | Gap description |
capture_quality: low on step | Poorly understood activity |
Step with notes containing "usually" or "sometimes" | Inconsistent execution |
| Single person as sole performer across >50% of steps | Key-person dependency |
Type 3 — Exception gaps
| Pattern | Gap description |
| Decision point with no exception path | Unhandled failure branch |
Exception in PIR with no handling | Undefined recovery procedure |
Exception path with owner_role_id empty | Unowned error handling |
Type 4 — Compliance gaps
| Pattern | Gap description |
controls empty on process | No governance controls |
Approval step with no approver role | Missing segregation of duties |
| High-risk exception with no escalation path | Escalation path undefined |
Severity Classification
| Severity | Description |
critical | Process cannot complete without this being resolved |
major | Significant risk of nonconformity or failure |
minor | Inconsistency or improvement opportunity |
observation | Informational — no immediate action required |
Exception Catalog
For each exception found, record:
exception_id— stable identifierdescription— what goes wrongtrigger_condition— what causes this exceptionaffected_steps[]— whichact-NNNIDs are affectedcurrent_handling— what the process does today (if anything)severity— critical | major | minor | observationrecommended_action— brief description (not a full solution)
Handoff Instruction
Pass gap-analysis.yaml and exception-catalog.yaml to future-state-and-change-strategy to prioritise gaps and design the target state.
Also use exception-catalog.yaml to enrich exception_paths[] in process-narrative-authoring.
References
Load on demand:
references/gap-analysis-framework.md— gap type taxonomy, severity classification, and root cause analysis templates
Scripts
scripts/analyze-gaps.mjs— detects structural, execution, exception, and compliance gaps from as-is-process.yaml
Assets
assets/fixtures/gap-analysis-example.yaml— canonical gap analysis for purchase-approval as-is process
About
Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

