agentleFS
yuusakuriyuusakuri/agent-skills/skills/discover-competitive-analysis/SKILL.md

discover-competitive-analysis

Skill2 starsChanged 10 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before entering a new market or launching a new product

    line 20
  2. Distinctive:

    When planning differentiation strategy for an existing product

    line 21
  3. Distinctive:

    When evaluating build vs. buy decisions

    line 23
  4. Distinctive:

    After losing deals to understand competitive positioning

    line 24
  5. Distinctive:

    When onboarding new product team members to the market context

    line 25
  6. Distinctive:

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

    line 36
  7. Distinctive:

    Create a comparison grid of key capabilities.

    line 45
  8. Very specific:

    Use the template in references/TEMPLATE.md to structure the output.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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 lean-canvas, or positioning-ideas 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.