gap-analysis
Gap Analysis
Overview
A gap analysis is a decision method, not a scorecard: define a bounded question, establish an observable current state, justify a desired state, compare them, explain why the difference exists, and decide what to do. A credible result makes evidence, assumptions, uncertainty, ownership, and trade-offs visible.
When to use
Load this skill when the work compares current and desired performance, capability, controls, process behavior, readiness, maturity, operating model, or research evidence and must produce an actionable artifact. Choose the variant from references/variants.md.
When not to use
Do not use this as a substitute for root-cause analysis, a risk assessment, SWOT, benchmarking, a requirements specification, a regulatory/legal opinion, or an audit/certification conclusion. Route technical capacity questions to capacity-and-cost-engineering, governance questions to ai-governance, and causal diagnosis to systematic-debugging or the relevant domain owner. A gap analysis may expose a need for those disciplines; it does not replace them.