feature-gap-analysis
Scannednpx machina-cli add skill Dragoon0x/Product-Skills/feature-gap-analysis --openclawFeature Gap Analysis
Identify which competitive feature gaps matter, which don't, and which should stay gaps.
How to use
/feature-gap-analysisApply gap analysis constraints to this conversation./feature-gap-analysis <competitors>Analyze gaps against named competitors.
Constraints
Feature Landscape
- Map every feature across three layers: must-have (table stakes), differentiating (changes deal outcomes), and nice-to-have (sounds impressive, rarely drives decisions)
- For each feature: Do we have it? (Yes / Partial / No / Planned) vs. each competitor
- MUST track how often each gap comes up in sales and support conversations
Gap Scoring
Score each missing feature on four dimensions:
- Customer demand (1-5): how often do customers ask for this?
- Revenue impact (1-5): does this gap cost you deals?
- Strategic importance (1-5): does this affect your positioning?
- Build effort (1-5, inverted — 5 means easy to build)
- Priority Score = (Demand + Revenue + Strategy) × Effort ÷ 3
Gap Classification
Every gap MUST go into one of four buckets:
- Close it: high priority, clear demand, reasonable effort. Put on the roadmap.
- Leapfrog it: don't match — build something better. Turn weakness into strength.
- Acknowledge it: not worth closing, but you need a story for when it comes up.
- Ignore it: low demand, low impact, high effort. Don't waste time.
- MUST explicitly classify. No ambiguous "maybe later" bucket.
Segment Mapping
- MUST map each gap to customer segments. A gap critical for Segment A may be irrelevant to Segment B.
- NEVER build for a segment you're not targeting just because a competitor has it
- If a gap only matters to a segment you don't serve, it's not actually your gap
Intentional Gaps
- Some gaps SHOULD stay gaps. Missing a feature that adds complexity can be an advantage.
- MUST document intentional gaps with reasoning
- Simplicity is a feature. Focus is a feature.
Anti-Patterns
- Building everything competitors have without asking if your users need it
- Treating all gaps as equal priority
- Never acknowledging gaps to the sales team, forcing them to improvise
- Confusing "they have it" with "our customers need it"
Source
git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/competitive-intelligence/feature-gap-analysis/SKILL.mdView on GitHub Overview
Feature Gap Analysis helps you identify which competitive gaps matter, which don’t, and which you should intentionally keep. It maps every feature across three layers (must-have, differentiating, nice-to-have), tracks how often gaps appear in sales and support conversations, and classifies gaps into four actionable buckets. The output guides roadmap decisions and build/buy/partner choices with clear segmentation alignment.
How This Skill Works
You map every feature across must-have, differentiating, and nice-to-have; compare your product against named competitors. For each missing feature, you score on four dimensions (customer demand, revenue impact, strategic importance, and build effort inverted so higher is easier) and compute a Priority Score. Then you classify each gap into one of four buckets (Close it, Leapfrog it, Acknowledge it, Ignore it), map gaps to customer segments, and document intentional gaps.
When to Use It
- When you're losing deals to missing features
- During roadmap planning with competitive context
- When evaluating build, buy, or partner decisions
- For sales enablement and objection handling
- When segmenting gaps to target specific customer groups
Quick Start
- Step 1: Run /feature-gap-analysis against named competitors
- Step 2: Map each feature into must-have, differentiating, and nice-to-have; compare across competitors
- Step 3: Score gaps, classify into buckets, align with segments, and document intentional gaps
Best Practices
- Map each feature across must-have, differentiating, and nice-to-have for every competitor
- Track how often each gap appears in sales and support conversations
- Explicitly classify each gap into one of the four buckets with no ambiguity
- Map gaps to relevant customer segments and avoid building for unserved segments
- Document intentional gaps and the rationale to preserve simplicity as a feature
Example Use Cases
- A company prioritizes closing must-have gaps to win enterprise deals rather than copying features
- They leapfrog competitors by delivering a differentiating capability that changes the deal outcome
- They acknowledge a low-impact gap and craft a credible sales narrative around it
- They ignore a high-effort gap that would complicate the product and delay time-to-market
- They map gaps to Segment A and deprioritize the same gaps for Segment B to focus on high-value targets
