okhp3-process-gap-analysis

Detect structural, execution, exception, and compliance gaps in as-is process YAML records.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-process-gap-analysis-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-process-gap-analysis
Source: https://github.com/OKHP3/telling-forward/tree/main/.agents/skills/okhp3-process-gap-analysis
Command: npx skills add https://github.com/OKHP3/telling-forward --skill okhp3-process-gap-analysis-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Business process documentation often hides missing steps, unowned activities, undefined exception handling, and absent controls. This Skill systematically analyzes a captured as-is process record to surface those gaps before future-state design begins, so improvement work is grounded in evidence rather than assumptions. ## Core Features & Use Cases - Four-type gap detection: Classifies gaps as structural (missing actors, boundaries), execution (inconsistent performance, key-person dependency), exception (undefined failure handling), or compliance (missing controls and segregation of duties). - Severity classification: Assigns critical, major, minor, or observation severity to each gap with root cause, impact, and recommended action. - Exception catalog generation: Produces a structured inventory of exceptions with trigger conditions, affected steps, and current handling. - Use Case: After capturing a purchase-approval process in as-is-process.yaml, run the analyzer to find that no controls are defined and one role performs over 50% of steps, then hand the gap report to future-state design. ## Quick Start Ask the agent to analyze the gaps in your as-is-process.yaml file and produce a gap analysis report and exception catalog.

Frequently Asked Questions about okhp3-process-gap-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find gaps in a business process document?▼

Run the analyze-gaps.mjs script against your as-is-process.yaml file with node scripts/analyze-gaps.mjs <as-is-process.yaml>. It returns typed gaps with severity, root cause, impact, and recommended actions as structured output.

What types of process gaps can be detected automatically?▼

The analyzer detects four gap types: structural gaps like steps with no actor role, execution gaps like low capture quality or key-person dependency, exception gaps with undefined handling, and compliance gaps like missing controls.

What input format does the gap analysis script require?▼

The script expects a parsed as-is-process.yaml object containing a steps array, and optionally controls and exceptions arrays. Each step should include an id, description, actor_role_id, and capture_quality fields for full analysis coverage.

When should I not run process gap analysis?▼

Do not run it before an as-is process capture exists, since the analysis depends on that upstream artifact. Also avoid using it to design solutions, because gap recording and future-state design are separate stages.

How are gap severity levels classified?▼

Gaps are classified as critical when the process cannot complete, major when there is significant nonconformity or failure risk, minor for inconsistencies, and observation for informational findings requiring no immediate action.