gap-analysislisted

## What this skill does Provides a repeatable framework for identifying and prioritising gaps between where things are now and where they need to be. It structures the analysis by dimension (process, data, technology, people, compliance, etc.), scores each gap by severity, and produces actionable recommendations with ownership. ## When to use it - User asks to "identify gaps", "do a gap analysis", or "compare current to target state". - User is preparing for a migration, transformation, audit, or initiative and needs to understand what needs to change. - User needs evidence to justify a project or roadmap item. - User wants to feed results into a `miro-board`, `risk-analysis`, or `tradeoff-analysis`. ## Key concepts ### Dimensions A gap analysis is organised by **dimension** — the aspect of the system or organisation being assessed. Choose dimensions that are relevant to the subject: | Dimension | What it covers | | --- | --- | | Process | How work is done; workflows, steps, handoffs | | Data | Data availability, quality, structure, lineage | | Technology | Tools, systems, integrations, infrastructure | | People | Skills, roles, capacity, knowledge | | Compliance | Regulatory, policy, or audit requirements | | Performance | SLAs, KPIs, benchmarks | | Documentation | Specs, runbooks, architecture records | ### Severity | Severity | Meaning | | --- | --- | | Critical | Blocks the target state; must close before proceeding | | High | Significant risk or rework if not ad