OM Gap Analysis

Add skill

Grounded gap analysis of requirements against the platform an app builds on — client docs become an Epic/Story tree whose every coverage verdict is re-run by executable gates against a validated platform checkout, scored in atomic commits, license-tier-tagged, summarized with a backlog. Use for "gap analysis", "what does the platform already cover".

Permissions

Files

SKILL.md

om-gap-analysis

Gap Analysis

Multi-document engagement scoping against a platform codebase. Turns a folder of client materials (transcripts, spec docs, requirement dumps) into an evidence-backed Epic/Story tree where every story carries a grounded verdict and an atomic-commit effort, then derives a client-facing summary and a prioritized backlog. The trust model is structural, not prose: subagents investigate, but every verdict is re-run by a deterministic gate against a validated, just-freshened local checkout of the platform — a subagent's claim is never written to the tree unverified. The method is generic; everything about a specific platform (repository, integration branch, companion repository, license tiers, capability catalog) is data, resolved from config and the platform's own knowledge. This skill verifies coverage; it does not author requirements or specs — and do that.

15 files · 155 KB9 KB

Version history

Gate	Layer	Binds
`bin/gap-checklist-gate`	intake	no Phase 2 on a happy-path-only tree
`bin/gap-orientation-preflight`	checkout	no grounding against a fork, wrong branch, or stale checkout
`bin/gap-validate-finding`	verdict	every verdict re-run locally; strawman queries rejected; the verdict symbol must agree with the block's per-criterion coverage rows (all/none/mixed → ✅/❌/🟡, every covered path existence-checked); tier derived from hit paths
`bin/gap-pipeline-crosscheck`	citation	no missed or phantom pipeline citations
`bin/gap-depth-check`	reporting	no significant cited PR buried outside the client-facing summary

OM Gap Analysis

Gap Analysis

Arguments

Workflow

Single-capability mode

Where artifacts live

The gates (executable, not prose)

Rules