Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.
Compares evidence-backed current and target states to prioritize bounded capability and readiness interventions.
--- name: gap-analysis description: >- Analyze gaps by comparing a defined current state with a justified target state, characterizing causes and uncertainty, prioritizing actionable interventions, and producing traceable matrices, roadmaps, and decision records. Use for capability, process, compliance, readiness, maturity, operating-model, or research-evidence gaps. Do not use for a vague list of problems, a standalone root-cause analysis, a generic SWOT, or legal or audit certification advice without a governing standard and qualified owner. license: MIT compatibility: Platform-agnostic methodology. No runtime dependency; optional Python 3 script uses only the standard library. metadata: tags: gap-analysis, current-state, target-state, capability, maturity, readiness, compliance, evidence, prioritization --- # 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. ## Core method 1. **Frame the decision.** State the decision or outcome, sponsor, population/system, time horizon, boundary, exclusions, and who will use the result. 2. **Define the criterion.** Make the target observable and source it to a requirement, outcome, benchmark, risk appetite, strategy, or explicitly labeled stakeholder preference. Do not invent a maturity scale or imply that a framework tier is a universal goal. 3. **Specify evidence.** For each dimension, define measure, unit, period, source, sampling, confidence, and acceptance rule before collecting data. Separate observed facts, reported perceptions, inferred causes, and assumptions. 4. **Describe the current state.** Use multiple relevant evidence types: records/metrics, direct observation, interviews, artifacts, tests, or research synthesis. Record missing and contradictory evidence instead of filling it with confidence. 5. **Compare like with like.** For every dimension, show current, target, difference, evidence, confidence, and consequence. A gap is a bounded difference, not merely a bad feeling or an absence of a preferred practice. 6. **Characterize the gap.** Distinguish outcome gap, capability/control gap, process gap, resource gap, knowledge/evidence gap, and decision/ownership gap. Keep root causes and proposed remedies separate from the observed gap. 7. **Prioritize transparently.** Use criteria appropriate to the decision, such as impact, urgency/exposure, reach, feasibility, dependency, cost, confidence, and reversibility. Show the rationale and do not hide value judgments inside a score. 8. **Plan closure.** Convert selected gaps into actions with a measurable closure condition, owner, dependencies, resources, date or review trigger, and residual risk. Assign an accountable decision-maker, not “the team.” 9. **Validate and revisit.** Review findings with affected stakeholders, test high-consequence claims, resolve material contradictions, and schedule a follow-up measurement. Closure means evidence that the target condition is met, not that an action was started. ## Required output shape Use `templates/gap-register.md` as the canonical row schema, then add only the context artifact needed: | Context | Add | |---|---| | Capability or maturity | `templates/capability-assessment.md` | | Process or operating model | `templates/process-gap-analysis.md` | | Compliance or readiness | `templates/compliance-readiness-assessment.md` | | Research or evidence | `templates/research-evidence-gap.md` | A useful report normally contains: executive decision, scope and method, target/criteria register, current-state evidence, gap register, prioritization logic, action roadmap, assumptions/unknowns, stakeholder review, and follow-up measure. Label hypothetical examples as hypothetical. ## Quality gates Before delivery, verify that each material gap has (a) a defined target and source, (b) current evidence or an explicit evidence gap, (c) a stated comparison and consequence, (d) a cause hypothesis distinguished from fact, (e) an owner and closure test, and (f) a priority rationale. Check that the report does not claim compliance, readiness, causation, or improvement without the evidence needed to support that claim. ## Reference routing | Load this file when... | Reference | |---|---| | You need the research-grounded method, evidence taxonomy, or source limits | `references/methodology.md` | | You need to choose among capability, process, compliance, readiness, maturity, or research variants | `references/variants.md` | | You need prioritization, scoring, sequencing, or closure controls | `references/prioritization-and-roadmaps.md` | | You need examples, anti-patterns, or review questions | `references/examples-and-anti-patterns.md` | | You need source provenance and claims behind this skill | `references/source-index.md` | | You need a structured checker for a completed JSON register | `scripts/validate-register.py` | ## Completion Stop when the decision question is answered by a reviewed, traceable artifact, or report the bounded unresolved evidence and the next collection action. Do not convert missing data into a green score or keep researching after the decision-relevant uncertainty is explicit.
Compares evidence-backed current and target states to prioritize bounded capability and readiness interventions.
The complete original method, source attribution and declared delivery limits.
Clarify the decision context and evidence, apply the framework, then name unresolved questions and accountable next steps.
Question, current evidence, target justification, constraints, governing standard and accountable owner.
Original documentation is published by Magnus Hedemark under the repository MIT license at the pinned revision. The unchanged original is supplied as planning guidance. Referenced files, scripts, runtimes and sibling skills are not bundled or installed. Validate current facts, legal/compliance interpretations, business metrics and operational decisions with accountable owners. Loading the text does not authorize deployments, code changes, customer outreach, account changes or other external actions.
Use Capability & Readiness Gap Analysis for [TASK]. Establish Question, current evidence, target justification, constraints, governing standard and accountable owner. Separate evidence from assumptions and return a bounded recommendation with open questions. Do not claim approval, execution or current facts without evidence.
Audit certification, unsupported maturity claims or automatic remediation.
M11 added German routing and scope limits. Original documentation is published by Magnus Hedemark under the repository MIT license at the pinned revision. The unchanged original is supplied as planning guidance. Referenced files, scripts, runtimes and sibling skills are not bundled or installed. Validate current facts, legal/compliance interpretations, business metrics and operational decisions with accountable owners. Loading the text does not authorize deployments, code changes, customer outreach, account changes or other external actions.
MIT License Copyright (c) 2026 Magnus Hedemark Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.