discover-competitive-analysis

$npx mdskill add product-on-purpose/pm-skills/discover-competitive-analysis

Creates a structured competitive analysis for product strategy

  • Identifies key competitors and their features, pricing, and positioning.
  • Depends on understanding market context and competitor data.
  • Uses a 2x2 matrix to visually compare and analyze competitors.
  • Delivers actionable strategic recommendations based on analysis.

SKILL.md

.github/skills/discover-competitive-analysisView on GitHub ↗
---
name: discover-competitive-analysis
description: Creates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations. Use before entering a market, planning differentiation, or after losing deals. For market size rather than competitor positioning, use discover-market-sizing instead.
license: Apache-2.0
metadata:
  phase: discover
  version: "2.2.0"
  updated: 2026-07-04
  category: research
  frameworks: [triple-diamond, lean-startup, design-thinking]
  author: product-on-purpose
---
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
# Competitive Analysis

A competitive analysis provides structured insight into the competitive landscape, helping product teams understand where they stand relative to alternatives and identify opportunities for differentiation. Rather than exhaustively cataloging every competitor, an effective analysis focuses on actionable insights that inform product strategy.

## When to Use

- Before entering a new market or launching a new product
- When planning differentiation strategy for an existing product
- During quarterly or annual strategic planning reviews
- When evaluating build vs. buy decisions
- After losing deals to understand competitive positioning
- When onboarding new product team members to the market context

## When NOT to Use

- You need market size rather than competitor positioning -> use `discover-market-sizing`
- You are stress-testing strategic differentiation across the whole business model -> use `foundation-lean-canvas`, or `tool-foundation-sprint-differentiation` inside a Foundation Sprint
- You want to understand why customers switch products -> use `define-jtbd-canvas`; it examines competing solutions through the job lens
- The landscape is already mapped and you need the problem framed -> use `define-problem-statement`

## Instructions

When asked to create a competitive analysis, follow these steps:

1. **Define the Scope**
   Clarify what you're analyzing: a specific feature area, overall product positioning, or pricing strategy. Identify 3-5 key competitors.direct competitors (same solution), indirect competitors (different solution to same problem), and potential disruptors.

2. **Gather Intelligence**
   Research each competitor through public sources: websites, pricing pages, G2/Capterra reviews, press releases, job postings, and customer testimonials. Note what you can verify vs. what you're inferring.

3. **Build the Feature Matrix**
   Create a comparison grid of key capabilities. Focus on features that matter to your target customers, not exhaustive checklists. Use consistent ratings (e.g., Full, Partial, None, Unknown).

4. **Analyze Positioning**
   Map competitors on a 2x2 positioning matrix using dimensions relevant to your market (e.g., price vs. features, ease of use vs. power, SMB vs. enterprise). Identify white space opportunities.

5. **Assess Strengths and Weaknesses**
   For each competitor, document genuine strengths (what they do better than you) and weaknesses (where they fall short). Avoid dismissing competitors.respect drives better strategy.

6. **Identify Strategic Implications**
   Translate observations into actionable recommendations: where to compete head-on, where to differentiate, what messaging to emphasize, and what gaps represent opportunities.

7. **Note Confidence Levels**
   Mark which conclusions are based on verified data vs. inference. Competitive intelligence has varying reliability.be honest about uncertainty.

## Output Format

Use the template in `references/TEMPLATE.md` to structure the output. A complete analysis fills every template section: Overview; Market Context; Competitors Analyzed; Feature Comparison Matrix; Pricing Comparison; Positioning Map; Competitor Deep Dives; Competitive Gaps and Opportunities; Strategic Recommendations; Sources and Confidence; and Next Steps.

## Quality Checklist

Before finalizing, verify:

- [ ] Scope is clearly defined (what market, segment, use case)
- [ ] 3-5 competitors are analyzed, including direct and indirect
- [ ] Feature comparison focuses on customer-relevant capabilities
- [ ] Positioning map uses meaningful, differentiated dimensions
- [ ] Strengths acknowledge where competitors genuinely excel
- [ ] Recommendations are specific and actionable
- [ ] Sources and confidence levels are documented

## Examples

See `references/EXAMPLE.md` for a completed example.

More from product-on-purpose/pm-skills

SkillDescription
define-hypothesisDefines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
define-jtbd-canvasCreates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
define-opportunity-treeCreates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.
define-prioritization-frameworkRun applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.
define-problem-statementCreates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
define-xFixture skill for phase-map and phase-router tests.
deliver-acceptance-criteriaGenerates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.
deliver-edge-casesDocuments edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.
deliver-launch-checklistCreates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release. Use for significant or cross-team launches, not a small single-team change. For the customer-facing announcement of what shipped, use deliver-release-notes instead.
deliver-prdCreates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.