MCPInstall

discover-competitive-analysis

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.

Installs
837
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/product-on-purpose/pm-skills --skill discover-competitive-analysis
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads discover-competitive-analysis automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

<!-- 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.

FAQ

What does the discover-competitive-analysis skill do?

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.

How do I install discover-competitive-analysis?

Run npx skills add https://github.com/product-on-purpose/pm-skills --skill discover-competitive-analysis in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/discover-competitive-analysis/ (personal) or .claude/skills/discover-competitive-analysis/ (project).

Which AI agents can use discover-competitive-analysis?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is discover-competitive-analysis safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains discover-competitive-analysis?

It is published by product-on-purpose in product-on-purpose/pm-skills. It has 837 recorded installs.

More from product-on-purpose/pm-skills

View all →

deliver-acceptance-criteria

product-on-purpose/pm-skills

Generates 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.

Testing & QA1.1K installs

deliver-prd

product-on-purpose/pm-skills

Creates 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.

deliver-user-stories

product-on-purpose/pm-skills

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.

deliver-edge-cases

product-on-purpose/pm-skills

Documents 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.

Testing & QA878 installs

define-problem-statement

product-on-purpose/pm-skills

Creates 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.

Business & Finance821 installs

define-hypothesis

product-on-purpose/pm-skills

Defines 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.

Testing & QA810 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.