Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Gap Analysis

  • 460 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

gap-analysis is a product-scoping prompt skill that compares current capabilities, competitor offerings, and target requirements for developers who need MVP priorities and missing-feature lists before committing to a bui

About

gap-analysis is a useful-ai-prompts skill that structures a capability comparison across what exists today, what competitors ship, and what the target product requires. Developers invoke it before locking MVP scope or sprint backlogs to surface missing features, misaligned priorities, and over-scoped commitments. The skill outputs a prioritized gap matrix—must-have versus nice-to-have features—with rationale tied to competitive positioning and user requirements. gap-analysis prevents build-phase rework by forcing explicit scope decisions while requirements are still cheap to change.

  • Current vs desired capability mapping
  • Competitive feature comparison matrices
  • Priority ranking and MVP cut lines
  • Risk and dependency identification
  • Actionable backlog recommendations

Gap Analysis by the numbers

  • 460 all-time installs (skills.sh)
  • Ranked #780 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill gap-analysis

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs460
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you define MVP scope with gap analysis?

Compare current capabilities, competitor offerings, and target requirements to define MVP scope, priorities, and missing features before build commitments.

Who is it for?

Developers or tech leads scoping a new product or major feature who need a structured comparison before writing implementation tickets.

Skip if: Skip gap-analysis when requirements are frozen, the project is pure maintenance, or competitive research has already been completed and documented.

When should I use this skill?

User needs MVP scoping, competitive feature comparison, or a prioritized list of missing capabilities before build starts

What you get

Prioritized gap matrix, MVP feature list, and missing-capability recommendations

  • gap analysis matrix
  • prioritized MVP feature list

Files

SKILL.mdMarkdownGitHub ↗

Gap Analysis

Table of Contents

Overview

Gap analysis systematically compares current capabilities with desired future state, revealing what needs to change and what investments are required.

When to Use

  • Strategic planning and goal setting
  • Technology modernization assessment
  • Process improvement initiatives
  • Skills and training planning
  • System evaluation and selection
  • Organizational change planning
  • Capability building programs

Quick Start

Minimal working example:

# Systematic gap identification

class GapAnalysis:
    GAP_CATEGORIES = {
        'Business Capability': 'Functions organization can perform',
        'Process': 'How work gets done',
        'Technology': 'Tools and systems available',
        'Skills': 'Knowledge and expertise',
        'Data': 'Information available',
        'People/Culture': 'Team composition and mindset',
        'Organization': 'Structure and roles',
        'Metrics': 'Ability to measure performance'
    }

    def identify_gaps(self, current_state, future_state):
        """Compare current vs desired and find gaps"""
        gaps = []

        for capability in future_state['capabilities']:
            current_capability = self.find_capability(
                capability['name'],
                current_state['capabilities']
            )

            if current_capability is None:
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Gap Identification FrameworkGap Identification Framework
Gap Analysis TemplateGap Analysis Template
Gap Closure PlanningGap Closure Planning
Communication & TrackingCommunication & Tracking

Best Practices

✅ DO

  • Compare current to clearly defined future state
  • Include all relevant capability areas
  • Involve stakeholders in gap identification
  • Prioritize by value and effort
  • Create detailed closure plans
  • Track progress to closure
  • Document gap analysis findings
  • Review and update analysis quarterly
  • Link gaps to business strategy
  • Communicate findings transparently

❌ DON'T

  • Skip current state assessment
  • Create vague future state
  • Identify gaps without solutions
  • Ignore implementation effort
  • Plan all gaps in parallel
  • Forget about dependencies
  • Ignore resource constraints
  • Hide difficult findings
  • Plan for 100% effort allocation
  • Forget about change management

Related skills

FAQ

What does gap-analysis output?

gap-analysis produces a prioritized gap matrix listing missing features, competitive deltas, and MVP must-haves versus deferrable items. Output is structured for direct conversion into implementation tickets and sprint backlog entries.

When should gap-analysis run in a project?

gap-analysis belongs before build commitments—during validate/scope—when current capabilities, competitor offerings, and target requirements need explicit comparison to prevent over-scoped MVPs and missed critical features.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.