Agent skill

Prd V02 Competitive Landscape Mapping

by mattgierhart in mattgierhart/PRD-driven-context-engineering

Map the competitive landscape before positioning your product for PRD v0.2 Market Definition.

MITAuto-check passedProduct & Project Management

Install Prd V02 Competitive Landscape Mapping

skills CLI
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-competitive-landscape-mapping -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v02-competitive-landscape-mapping --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-v02-competitive-landscape-mapping .claude/skills/prd-v02-competitive-landscape-mapping && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prd-v02-competitive-landscape-mapping
GitHub stars
180
Token cost
~2.3k tokens
SKILL.md length
728 words
Files
5 (incl. references, assets)
Skills in repo
45
Repo updated
First seen
Licence
MIT

At a glance

Map the competitive landscape before positioning your product for PRD v0.2 Market Definition.

  • Works in 5 steps: Document Current Behavior → Competitor Discovery → Gap Analysis → …
  • Completing v0.1 Spark
  • SKILL.md covers Workflow Position, Consumes, Produces and Workflow Overview, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prd V02 Competitive Landscape Mapping is an agent skill from mattgierhart/PRD-driven-context-engineering. 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.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `assets/feature-matrix.md`, `assets/landscape.md` and `references/examples.md`).

It sits in Product & Project Management, covering Competitor analysis, PRD writing and Physical and earth sciences. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.

When your agent uses it

  • Completing v0.1 Spark
  • Analyzing competitors
  • Researching market
  • Requests like competitive analysis

Example prompts

  • “competitive analysis”
  • “who else solves this”
  • “market landscape”
  • “/prd-v02-competitive-landscape-mapping”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, WebSearch, WebFetch

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Document Current Behavior
  2. Competitor Discovery
  3. Gap Analysis
  4. Feature Comparison Matrix
  5. 1% Better Hypothesis

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • WebSearch
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd V02 Competitive Landscape Mapping loads about 2.3k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 728 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 728 words, ~2,327 tokens.

Download SKILL.mdSave it as .claude/skills/prd-v02-competitive-landscape-mapping/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
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.
allowed-tools
Read, Write, Edit, Glob, Grep, WebSearch, WebFetch
context
fork

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)

Consumes

This skill requires prior work from v0.1:

  • **CFD-* entries (problem statements, from Problem Framing) — Evidence for what users need/want
  • **CFD-* entries (value hypotheses, from User Value Articulation) — Desired outcomes users are seeking
  • PRD.md Why section — Problem framing and market signals

This skill assumes v0.1 Spark is complete (both problem and value).

Produces

This skill creates/updates:

  • CFD-* entries (competitive intelligence) — Analysis of direct competitors, adjacent solutions, workarounds
  • BR-* entries (positioning rules) — Constraints derived from landscape analysis
  • Landscape map artifact — Current behavior documentation, feature matrix, 1% better hypothesis

All CFD competitive intelligence entries should include:

  • confidence: 2-3/5 (based on evidence tier from public sources + user validation)
  • Evidence source (G2 reviews, pricing pages, user interviews, etc.)
  • Forward target: "Would move to 4/5 if we validate gap with 5+ target users"

Example competitive intelligence entry:

markdown
CFD-042: Competitive Intelligence — Competitor Landscape Analysis

Type: Competitive Intelligence
Date: 2026-02-01
Confidence: 3/5 (source: public-research + 3-customer-interviews)
Competitors Analyzed: 4 direct + 2 adjacent
Primary Gap: All competitors require enterprise licensing; SMB segment underserved

Feature Matrix: [Link to matrix]
1% Hypothesis: "SMB sales teams can get 80% of [Competitor A] features for 40% of price"
Evidence:
  - CFD-001: 3 SMB teams paying $500/mo but using only 5 of 20 features
  - CFD-015: Value hypothesis shows $12,500/year need for core 5 features only
Next Target: "Would move to 4/5 if we validate with 5+ SMB prospects willing to pay $200/mo"

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)
Show full SKILL.md (284 more words)Show less

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?)

© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references, assets) in .claude/skills/prd-v02-competitive-landscape-mapping of mattgierhart/PRD-driven-context-engineering.

  • SKILL.md
  • assets/feature-matrix.md
  • assets/landscape.md
  • references/examples.md
  • references/research-prompts.md

Open the folder on GitHubat commit 30ed1b0

Compare with similar skills

Prd V02 Competitive Landscape Mapping next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd V02 Competitive Landscape Mapping compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd V02 Competitive Landscape Mapping this skillmattgierhart/PRD-driven-context-engineering180—~2.3kAutomated safety check: PassMIT
Product Developmentgustavscirulis/snapgrid1161 repos~1.1kAutomated safety check: PassCustom licence
PRD GeneratorFokkyp/claude-skills226—~1.9kAutomated safety check: PassNone
Product Managementooiyeefei/ccc495—~1.8kAutomated safety check: PassMIT
Product Competitive AnalysisFokkyp/claude-skills226—~1.2kAutomated safety check: PassNone
Screenshot Feature Extractordavila7/claude-code-templates33k1 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Product Development

    gustavscirulis/snapgrid

    End-to-end product development for iOS/macOS apps. An agent skill from gustavscirulis/snapgrid.

    116 GitHub starsUsed in 1 repo~1.1k tokens
    Product & Project ManagementAuto-check passed
  • PRD Generator

    Fokkyp/claude-skills

    Guides a product manager from a rough idea to a structured PRD through interview questions, competitor research, module feedback and iterative revision.

    226 GitHub stars~1.9k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Product Management

    ooiyeefei/ccc

    This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap"…

    495 GitHub stars~1.8k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed
  • Product Competitive Analysis

    Fokkyp/claude-skills

    Produces product-manager competitive analysis reports in Chinese, with a confirm-first scoping gate, three-phase evidence collection and single or multi-product modes.

    226 GitHub stars~1.2k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Screenshot Feature Extractor

    davila7/claude-code-templates

    Analyze product screenshots to extract feature lists and generate development task checklists.

    33k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Pre Mortem

    phuryn/pm-skills

    Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.

    27k GitHub stars~1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from mattgierhart/PRD-driven-context-engineering

All 45 skills in this repo
  • Ghm Gate Check

    mattgierhart/PRD-driven-context-engineering

    Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).

    180 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Ghm Harvest

    mattgierhart/PRD-driven-context-engineering

    Extracts durable insights from temp/ files to SoT during EPIC Phase E.

    180 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Ghm Id Register

    mattgierhart/PRD-driven-context-engineering

    Validates and registers new SoT IDs with cross-reference integrity.

    180 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Ghm Sot Builder

    mattgierhart/PRD-driven-context-engineering

    Creates new Source of Truth (SoT) files when existing templates don't fit your needs.

    180 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V01 Problem Framing

    mattgierhart/PRD-driven-context-engineering

    Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.

    180 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V01 User Value Articulation

    mattgierhart/PRD-driven-context-engineering

    Transform validated pain points into articulated user value statements for PRD v0.1 Spark.

    180 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Prd V02 Competitive Landscape Mapping

What does Prd V02 Competitive Landscape Mapping do?

Map the competitive landscape before positioning your product for PRD v0.2 Market Definition. Prd V02 Competitive Landscape Mapping is an agent skill from mattgierhart/PRD-driven-context-engineering.2 Market Definition.

When should I use Prd V02 Competitive Landscape Mapping?

Prd V02 Competitive Landscape Mapping fits situations like: completing v0.1 Spark; analyzing competitors; researching market; requests like competitive analysis.

How do I install Prd V02 Competitive Landscape Mapping in Claude Code?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-competitive-landscape-mapping -a claude-code`. Or copy the skill folder (.claude/skills/prd-v02-competitive-landscape-mapping in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v02-competitive-landscape-mapping in your project. Claude Code loads it when a task matches its description.

How do I install Prd V02 Competitive Landscape Mapping in Codex?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-competitive-landscape-mapping -a codex`. Or copy the skill folder (.claude/skills/prd-v02-competitive-landscape-mapping in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v02-competitive-landscape-mapping in your project. Codex loads it when a task matches its description.

Can I use Prd V02 Competitive Landscape Mapping in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v02-competitive-landscape-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-v02-competitive-landscape-mapping, .gemini/skills/prd-v02-competitive-landscape-mapping, .github/skills/prd-v02-competitive-landscape-mapping and .opencode/skills/prd-v02-competitive-landscape-mapping in your project.

What does Prd V02 Competitive Landscape Mapping need to run?

SKILL.md names no scripts, command-line tools or credentials: Prd V02 Competitive Landscape Mapping is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, WebSearch, WebFetch.

Does Prd V02 Competitive Landscape Mapping access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prd V02 Competitive Landscape Mapping safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prd V02 Competitive Landscape Mapping use?

Prd V02 Competitive Landscape Mapping is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd V02 Competitive Landscape Mapping use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Prd V02 Competitive Landscape Mapping?

Skills that share tags, products or a category with Prd V02 Competitive Landscape Mapping: Product Development (gustavscirulis/snapgrid, 116 stars), PRD Generator (Fokkyp/claude-skills, 226 stars), Product Management (ooiyeefei/ccc, 495 stars) and Product Competitive Analysis (Fokkyp/claude-skills, 226 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd V02 Competitive Landscape Mapping?

mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.

Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.