Back to list
mattgierhart

prd-v02-competitive-landscape-mapping

by mattgierhart

PRD-driven Context Engineering: A systematic approach to building AI-powered products using progressive documentation and context-aware development workflows

9🍴 2📅 Jan 24, 2026

SKILL.md


name: prd-v02-competitive-landscape-mapping description: > Map the competitive landscape before positioning your product for PRD v0.2 Market Definition. Triggers on completing v0.1 Spark, analyzing competitors, researching market, or requests like "competitive analysis", "who else solves this", "market landscape", "what alternatives exist", "competitor research", "feature comparison". Outputs CFD- entries for competitive intelligence and BR- entries for positioning rules.

Competitive Landscape Mapping

Understand market reality before defining your position.

Workflow Position

v0.1 Spark (Problem + Value) → Competitive Landscape Mapping → Product Type Classification
       (what hurts)                 (who else solves it)           (how we compete)

Input: Problem statements (CFD-) and value hypotheses (CFD-) from v0.1 Output: Landscape map, feature matrix, 1% better hypothesis (CFD-, BR-)

Workflow Overview

  1. Document current behavior → What users do TODAY (before competitor search)
  2. Discover alternatives → Direct, adjacent, workarounds, "do nothing"
  3. Analyze gaps → Industry/geography gaps, underserved segments
  4. Compare features → Build comparison matrix
  5. Form hypothesis → 1% better hypothesis with evidence

Core Output Template

ElementDefinitionEvidence
Current BehaviorHow users solve this todayObserved workflow
Direct CompetitorsProducts solving same problemRevenue/funding proof
Adjacent SolutionsProducts solving related problemsUser overlap
WorkaroundsDIY solutions (spreadsheets, manual)Forum/reddit mentions
Feature MatrixSide-by-side capability comparisonProduct documentation
Gap AnalysisWhere competition is weakReviews, complaints
1% HypothesisHow we winEvidence-anchored

See assets/landscape.md for copy-paste template.

Step 1: Document Current Behavior

Before searching competitors, document what target users do TODAY.

Capture Format

Current Behavior: [What they do]
Tools Used: [Existing tools, if any]
Time Investment: [Hours/week on workaround]
Pain Points: [From v0.1 CFD-IDs]

Why First?

  • Prevents solution bias from competitor features
  • Reveals workarounds competitors might miss
  • Establishes true baseline for improvement claims

Step 2: Competitor Discovery

Discovery Categories

CategoryDefinitionSearch Strategy
DirectSame problem, same segment"[problem] software"
AdjacentRelated problem, potential pivot"[related workflow] tool"
WorkaroundsDIY solutionsReddit: "how I [task]"
Do NothingAccept status quoWhy hasn't this been solved?

Minimum Discovery Checklist

  • 3+ direct competitors (or document why fewer exist)
  • 2+ adjacent solutions
  • 1+ workaround documented
  • "Do nothing" cost quantified

Create CFD Entry Per Competitor

CFD-###: Competitor — [Name]
Type: Competitive Intelligence
Source: [Website, G2, Crunchbase]
Date: YYYY-MM-DD

Overview: [1-2 sentences]
Target Segment: [Who they serve]
Pricing: [Model and range]
Revenue/Funding: [If available]
Key Differentiator: [Their claim]
Weakness Signals: [Reviews, complaints]

Step 3: Gap Analysis

Industry/Geography Gap Table

IndustryCompetitors ServingGap Level
[Industry 1]X of YNone / Small / Large
[Industry 2]X of YNone / Small / Large

Segment Gap Table

SegmentServed ByUnderserved Signal
Enterprise[List][Signal or "Well served"]
Mid-Market[List][Signal or "Well served"]
SMB[List][Signal or "Well served"]
Prosumer[List][Signal or "Well served"]

Underserved Signals

  • Tier 1: Users paying but complaining (G2 reviews)
  • Tier 2: Users building workarounds (Reddit, forums)
  • Tier 3: Users asking for solutions (community posts)
  • Tier 4: No apparent demand (caution)

Step 4: Feature Comparison Matrix

Build side-by-side comparison:

FeatureUs (Planned)Competitor ACompetitor BGap
[Feature 1]✅/❌/🔄✅/❌✅/❌[Our advantage]
[Feature 2]✅/❌/🔄✅/❌✅/❌[Our advantage]

Legend: ✅ = Has | ❌ = Missing | 🔄 = Planned

Matrix Requirements

  • Include all "table stakes" features (what everyone has)
  • Identify 1-3 differentiating features
  • Note pricing tier where features unlock
  • Flag features competitors are building (roadmap signals)

Step 5: 1% Better Hypothesis

Template

We can be 1% better than [Competitor X] by [specific improvement] for [specific segment].

Evidence:
- [CFD-ID]: [Supporting evidence]
- [CFD-ID]: [Supporting evidence]

Why This Matters:
- [Segment] cares about this because [reason]
- Current solutions fail at this because [reason]

Risk:
- [What could invalidate this hypothesis]

Hypothesis Quality Check

  • "1% better" is specific and measurable
  • References CFD-IDs for evidence
  • Targets a defined segment
  • Explains WHY this gap exists
  • Acknowledges risks

Quality Gates

Pass Checklist

  • ≥3 competitors documented with CFD-IDs
  • Feature matrix with ≥5 compared features
  • ≥1 gap identified with Tier 1-2 evidence
  • 1% better hypothesis formed
  • Current behavior documented FIRST

Testability Check

  • Can validate 1% hypothesis in <30 days?
  • Can find 10 people in target segment?
  • Gap evidence is from users, not assumptions?

Anti-Patterns

PatternSignalFix
Competitor-first thinkingStarted with competitor featuresDocument current behavior first
False uniqueness"No competitors" claimInclude workarounds and adjacent
Feature bloatMatrix has 20+ featuresFocus on differentiators
Vague gaps"Better UX" without evidenceAdd specific user complaint
10x claims"10x better than X"Start with 1% provable claim
Ignored workaroundsOnly listed software competitorsInclude spreadsheets, manual

CFD/BR Output Format

CFD Entry (Competitive Intelligence)

CFD-###: Competitive Intelligence — [Market/Segment]
Type: Competitive Intelligence
Date: YYYY-MM-DD

Competitors Analyzed: [Count]
Primary Gap: [Description]
Evidence Tier: [1-5]

Feature Matrix: [Link or inline]
1% Hypothesis: [Statement]

BR Entry (Positioning Rule)

BR-###: Positioning Rule — [Title]
Type: Business Rule
Source: CFD-###
Date: YYYY-MM-DD

Rule: [Specific constraint derived from landscape]
Rationale: [Why this matters]
Applies To: [Scope]

Bundled Resources

  • references/research-prompts.md — Deep research templates for competitor discovery and gap analysis.
  • references/examples.md — Good/bad competitive analysis examples.
  • assets/landscape.md — Copy-paste template for landscape mapping.
  • assets/feature-matrix.md — Feature comparison matrix template.

Handoff

Competitive landscape complete when quality gates pass. Landscape map informs:

  • Product Type Classification (next skill) — What type are we? Clone, Slice, etc.
  • v0.3 Pricing — Competitive pricing anchors
  • v0.3 Moat — Where competitors are weak

Next: Product Type Classification (How should we compete based on landscape?)

Score

Total Score

75/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon