competitive-analysis

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill competitive-analysis
0 commentsdiscussion
summary

Framework-driven competitive analysis grounded in market realities, not feature comparison.

  • Expands competitive set beyond direct competitors to include status quo, workarounds, and analog alternatives; helps identify the true threat (features, distribution, or business model)
  • Surfaces structural asymmetries and unique advantages competitors cannot easily copy, with emphasis on grounding analysis in customer and market perspective rather than internal politics
  • Flags common pitfalls:
skill.md

Competitive Analysis

Help the user understand competitive dynamics using frameworks from 49 product leaders who have navigated competition at companies from startups to Netflix and Google.

How to Help

When the user asks for help with competitive analysis:

  1. Expand the competitive set - Identify not just direct competitors but the status quo and workarounds
  2. Understand the true threat - Determine if the competition is features, distribution, or fundamental business model
  3. Find asymmetries - Help them identify unique advantages competitors cannot easily copy
  4. Design the right response - Balance competitive awareness with customer obsession

Core Principles

Compete against the status quo

April Dunford: "Most folks will discount the status quo, but they shouldn't because in B2B we lose about 40% of our deals to 'no decision,' which actually means we lost to the spreadsheet, we lost to pen and paper." Position specifically against current workarounds, not just competitors.

Define competitive alternatives first

April Dunford: "The first step in a good positioning exercise is to really understand, what do we have to position against? What do I have to beat in order to win a deal?" Look beyond direct competitors to anything customers would do if your product didn't exist.

Understand industry economics deeply

Hamilton Helmer: "Understanding whether or not there is a type of power in place is hard... the hard part is industry economics, what really are the economic relationships." Surface-level competitive analysis misses the structural forces that determine winners.

Ground everything in external reality

Shaun Clowes: "In everything always talk from the customer's perspective, from the market's perspective, from the competitor's perspective. The very small number of PMs do that." Great PMs differentiate by grounding work in market realities, not internal politics.

Include the analog alternative

Bret Taylor: "Why use this instead of Yahoo Yellow Pages? But more than anything else, why use this instead of the Yellow Pages?" Compete against the traditional, non-digital way users solve the problem.

Competition includes workarounds

Jake Knapp: "What's the competition for solving that problem? How do they solve it today? And what are the alternatives? What are the workarounds?" Look beyond direct startup competitors to manual processes and existing habits.

Don't blindly copy competitors

Elena Verna: "Knowing what your competition is doing is extremely important... But blatantly copying all of these best tactics or flows because they're doing better than us - that's where things really go wrong." Use competitors for inspiration, not replication.

Beware competitive myopia

Tanguy Crusson: "Your competitor, if you think of what they do as an iceberg, the top side is what they've shipped in terms of features, but it's based on all this stuff they've built in terms of research." You only see their past output, not their underlying strategy.

Questions to Help Users

  • "What would your customer do if your product didn't exist?"
  • "What percentage of deals do you lose to 'no decision'?"
  • "What's the weakness in your competitor's greatest strength?"
  • "Is your advantage in features, distribution, or business model?"
  • "How would a competitor describe your positioning?"
  • "What market 'current' are you riding or fighting against?"

Common Mistakes to Flag

  • Ignoring the status quo - 40% of B2B deals are lost to doing nothing, not to competitors
  • Feature-by-feature comparison - Distribution moats often matter more than feature sets
  • Fast-following without context - Competitor features reflect year-old thinking, not current strategy
  • Assuming data creates moats - Data advantages often diminish once competitors reach scale
  • Over-indexing on competitors - Great for market awareness, dangerous for product roadmap

Deep Dive

For all 63 insights from 49 guests, see references/guest-insights.md

Related Skills

  • Writing North Star Metrics
  • Defining Product Vision
  • Prioritizing Roadmap
  • Setting OKRs & Goals
how to use competitive-analysis

How to use competitive-analysis on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add competitive-analysis
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill competitive-analysis

The skills CLI fetches competitive-analysis from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/competitive-analysis

Reload or restart Cursor to activate competitive-analysis. Access the skill through slash commands (e.g., /competitive-analysis) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.567 reviews
  • Ren Singh· Dec 28, 2024

    I recommend competitive-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • William Gonzalez· Dec 20, 2024

    competitive-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Jin Verma· Dec 20, 2024

    Registry listing for competitive-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Camila Ndlovu· Dec 12, 2024

    Keeps context tight: competitive-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Pratham Ware· Dec 4, 2024

    competitive-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 23, 2024

    Solid pick for teams standardizing on skills: competitive-analysis is focused, and the summary matches what you get after install.

  • Ava Khanna· Nov 23, 2024

    competitive-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Arjun Kapoor· Nov 19, 2024

    competitive-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ren Ghosh· Nov 19, 2024

    Useful defaults in competitive-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Charlotte Shah· Nov 15, 2024

    competitive-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 67

1 / 7