From pm
Use when making a product or business decision where knowing the competitive context changes the answer — before a launch, when writing strategy, or when articulating differentiation. Triggers on: "competitor analysis", "competitive landscape", "how do we differentiate", "who are our competitors", "경쟁사 분석", "시장 분석", "차별화 전략". Best for: pre-launch competitive positioning, PRD strategic context, GTM messaging differentiation. Not for: internal tools with no external competitors; user research on what customers want (shows what competitors built, not what users need).
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm:competitive-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Competitive analysis answers three questions:
Competitive analysis answers three questions:
This skill produces two artifacts: Competitor Profiles and a Positioning Gap Summary.
../prd-development/SKILL.md../product-discovery/SKILL.md surfaces competitive gaps as an opportunity../go-to-market-planning/SKILL.md../pricing-monetization-strategy/SKILL.mdBefore analyzing anything, define scope.
| Type | Definition | Example |
|---|---|---|
| Direct | Same target user, same problem, similar solution | Figma vs Sketch |
| Indirect | Same problem, different solution or delivery model | Notion vs. Confluence |
| Substitute | Different framing, but competes for the same job-to-be-done | Excel vs. Airtable |
| Emerging | Early-stage or category-adjacent players to watch | New AI-native entrants |
Action: List 3-8 competitors across these types. Avoid the trap of only analyzing the most obvious direct competitor.
For each competitor, collect:
Create a table with competitors as columns and key capabilities as rows.
| Capability | Us | Competitor A | Competitor B | Competitor C |
|---|---|---|---|---|
| [Core capability 1] | ✓ | ✓ | ✗ | ✓ |
| [Core capability 2] | ✓ | ✗ | ✓ | ✗ |
| [Core capability 3] | Partial | ✓ | ✓ | ✗ |
| [Differentiating capability] | ✓ | ✗ | ✗ | ✗ |
| [Table stakes capability] | ✓ | ✓ | ✓ | ✓ |
| Pricing model | — | — | — | — |
| Entry price | — | — | — | — |
| Target segment | — | — | — | — |
Reading the matrix:
A 2x2 positioning map shows where each player sits on two axes that matter to your target customer.
Pick axes that:
Common axis pairs:
HIGH [Axis Y]
|
[B] | [A]
|
--------+--------
|
[C] | [D = Us]
|
LOW | HIGH [Axis X]
Label each competitor's position and annotate why they sit there.
A focused SWOT — skip generic platitudes, focus on actionable insights.
| Internal | External | |
|---|---|---|
| Positive | Strengths: What we do better than anyone in this space | Opportunities: Gaps competitors aren't serving; emerging needs |
| Negative | Weaknesses: Gaps in our current offering vs. market expectation | Threats: Competitor moves, commoditization risk, category shifts |
Rule: Each cell should have 2-4 specific, evidence-backed points. No vague statements like "strong team."
Based on the feature matrix, positioning map, and SWOT-lite, answer:
| Strategy | When It Works | Risk |
|---|---|---|
| Feature superiority | Competitors are weak in a critical area you can own | Easy to copy |
| Segment focus | Broad competitors ignore a specific segment's real needs | Small TAM |
| UX/simplicity | Incumbents are complex; your user wants ease over power | Hard to justify to enterprise |
| Ecosystem / integrations | Your user lives in a specific stack; you integrate better | Dependency risk |
| Price disruption | Premium market with underserved price-sensitive segment | Margin pressure |
| Vertical depth | Horizontal tools ignore domain-specific workflows | Niche ceiling |
## [Competitor Name]
**Type:** Direct / Indirect / Substitute / Emerging
**Target User:** [Who they build for]
**Core Value Prop:** [Their own words or closest paraphrase]
**Entry Price:** [Tier name + price]
**Pricing Model:** [Freemium / seat-based / usage-based / etc.]
### Key Capabilities
1. [Capability]
2. [Capability]
3. [Capability]
### Known Weaknesses
- [Source: G2/Capterra/community]
- [Source: G2/Capterra/community]
### Recent Moves
- [Date]: [What they announced/shipped/raised]
### Positioning in One Sentence
[Company] is the [category] for [user] who needs [value], unlike [comparison] which [contrast].
## Positioning Gap Summary
### Table Stakes (must-have, not differentiating)
- [List features every player has]
### Our Differentiators (we have, competitors don't)
- [Feature/capability]: [Why it matters to the target user]
### Gaps to Evaluate (competitors have, we don't)
- [Feature/capability]: [Build / Partner / Ignore + rationale]
### Whitespace Opportunity
[Description of the positioning we can credibly own and why]
### Our "Only We" Statement
Only [Company] can [capability] for [user] because [reason].
../prd-development/SKILL.md../go-to-market-planning/SKILL.md../pricing-monetization-strategy/SKILL.md../product-discovery/SKILL.md| Claude | You |
|---|---|
| Builds competitor profile templates and feature matrix | Performs actual product trials and gathers pricing data |
| Drafts positioning map axes and whitespace analysis | Validates positioning with real customer interviews |
| Generates "Only We" statement drafts | Makes the final differentiation call based on business context |
| Identifies anti-patterns and strategic blind spots | Decides which competitive gaps are worth pursuing |
| Connects findings to PRD, GTM, and pricing frameworks | Synthesizes with internal knowledge not available to Claude |
If no prior competitive research exists, provide:
| Anti-Pattern | Symptom | Fix |
|---|---|---|
| Only analyzing the most famous competitor | Analysis ignores the actual alternatives your users consider | Ask users "what did you use before / what else did you evaluate?" |
| Copying competitor features | Feature matrix becomes a copy list | Use matrix to identify gaps worth owning, not a checklist to replicate |
| Positioning on hygiene factors | "We're the most secure / most reliable" | Security and reliability are expected, not differentiating — find the real trade-off |
| Stale analysis | Competitive landscape from 18 months ago | Set a calendar reminder to refresh quarterly; check changelogs monthly |
| Ignoring negative reviews | Only reading what competitors say about themselves | G2 1-star reviews are your best market research |
../prd-development/SKILL.md — Paste the Positioning Gap Summary into Phase 4 (Strategic Context)../go-to-market-planning/SKILL.md — "Only We" statement and differentiators become GTM core messaging../pricing-monetization-strategy/SKILL.md — Competitor pricing tiers feed the pricing model analysis../product-discovery/SKILL.md — Validate competitive gaps as real user needsnpx claudepluginhub newkayak12/claude-skills --plugin pmCreates a structured competitive analysis comparing features, positioning, and strategy across competitors. Use when entering a market, planning differentiation, or understanding the competitive landscape.
Conducts competitive product analysis to deliver positioning calls: where to play, how to win. Use for competitor analysis, landscape mapping, or comparison queries.
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".