porters-five-forces

phuryn/pm-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/phuryn/pm-skills --skill porters-five-forces
0 commentsdiscussion
summary

You are a competitive strategist conducting a Porter's Five Forces analysis for $ARGUMENTS.

skill.md

Porter's Five Forces

Metadata

  • Name: porters-five-forces
  • Description: Perform a Porter's Five Forces analysis evaluating competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants.
  • Triggers: Porter's five forces, competitive forces, industry analysis, market forces, competitive dynamics

Instructions

You are a competitive strategist conducting a Porter's Five Forces analysis for $ARGUMENTS.

Your task is to evaluate the structural attractiveness of an industry and identify the competitive dynamics that will determine profitability.

Input Requirements

  • Industry or market definition
  • Current competitors and competitive positioning
  • Supplier and customer landscape
  • Potential substitutes and new entrants
  • Product or service specifics

Porter's Five Forces Framework

1. Competitive Rivalry (How intense is competition?)

The degree to which companies compete directly for market share and customers.

High Rivalry When:

  • Many competitors of similar size and strength
  • Slow industry growth (zero-sum competition)
  • Low product differentiation (commoditized)
  • High fixed costs (pressure to maintain volume)
  • Exit barriers are high (expensive to leave)
  • Price competition is intense
  • Rivals have diverse strategies and goals
  • Emotional or strategic commitments keep rivals fighting

Low Rivalry When:

  • Few competitors
  • High growth market
  • High differentiation (less price-sensitive)
  • Low fixed costs
  • Low switching costs for competitors
  • Industry leader has clear dominance
  • Rivals are cooperative or have compatible goals

Strategic Implications:

  • Assess competitive positioning and differentiation
  • Define defensible competitive advantages
  • Monitor competitor moves and market consolidation
  • Invest in differentiation or cost leadership

2. Supplier Power (How much power do suppliers have?)

The ability of suppliers to increase prices or reduce quality, affecting your profitability.

High Supplier Power When:

  • Few suppliers or concentrated supplier base
  • Switching costs are high (changing suppliers is expensive)
  • Backward integration threat (suppliers become competitors)
  • Suppliers' product is critical or unique
  • Suppliers have strong bargaining position
  • No substitutes for supplier offerings
  • Suppliers sell to many industries (less dependent on you)

Low Supplier Power When:

  • Many suppliers available
  • Low switching costs
  • Suppliers depend on your business
  • Commodity products (interchangeable suppliers)
  • Threat of forward integration (you become your own supplier)
  • Available substitutes for supplier offerings
  • You have significant bargaining leverage

Strategic Implications:

  • Diversify supplier base to reduce dependency
  • Build strong supplier relationships
  • Consider vertical integration or alternatives
  • Negotiate long-term contracts with favorable terms
  • Invest in suppliers' success (partnerships)

3. Buyer Power (How much power do customers have?)

The ability of customers to negotiate lower prices or demand higher quality, affecting your margin.

High Buyer Power When:

  • Few large customers (concentrated demand)
  • Buyers switch easily and often (low switching costs)
  • Backwards integration threat (customers become competitors)
  • Product is undifferentiated (commoditized)
  • Buyers have price sensitivity or tight budgets
  • Buyers have full information about alternatives
  • Customers can bypass you entirely

Low Buyer Power When:

  • Many fragmented customers
  • High switching costs (lock-in, integration, training)
  • High product differentiation (fewer alternatives)
  • Customers depend on your product
  • You have strong brand or reputation
  • Switching to alternatives involves risk
  • Customers lack information about alternatives

Strategic Implications:

  • Build strong customer relationships and loyalty
  • Create switching costs through integration
  • Invest in brand and differentiation
  • Develop customer success programs
  • Create network effects or communities
  • Segment customers by willingness to pay

4. Threat of Substitutes (Are there alternative solutions?)

The risk that customers will switch to alternative products that solve the same problem.

High Threat When:

  • Good substitutes exist and are easily accessible
  • Substitutes have similar performance or better value
  • Switching costs to substitutes are low
  • Customers are willing to try alternatives
  • Substitutes are improving faster than your product
  • Price-to-performance of substitutes is attractive
  • Substitute technology is disruptive or emerging

Low Threat When:

  • No good substitutes exist
  • Substitutes are more expensive or inferior
  • Switching costs are high
  • Your product is deeply integrated into customer workflows
  • Customer preference and loyalty are strong
  • Barrier to substitute entry are high
  • Your product solves the problem uniquely

Strategic Implications:

  • Monitor emerging substitutes and disruptive technologies
  • Build customer stickiness through integration and loyalty
  • Invest in product innovation and improvement
  • Create switching costs through ecosystem or community
  • Diversify into adjacent or complementary products
  • Defend through brand, service, or convenience

5. Threat of New Entrants (Can new competitors easily enter?)

The risk that new competitors will enter the market and capture share.

High Threat When:

  • Low barriers to entry (capital, expertise, licensing)
  • Attractive industry margins and growth
  • Incumbents are vulnerable or complacent
  • Distribution or channel access is available
  • Economies of scale are limited
  • Network effects are weak or absent
  • Regulation is permissive
  • New technologies enable disruption

Low Threat When:

  • High barriers to entry (capital, IP, expertise, relationships)
  • Entrenched incumbents with scale advantages
  • Strong network effects or switching costs
  • Brand loyalty is high
  • Regulatory or licensing barriers exist
  • Economies of scale create cost advantage
  • Control of critical resources or distribution
  • Retaliation by incumbents is credible

Strategic Implications:

  • Build defensible barriers (IP, brand, network effects)
  • Establish cost leadership and scale advantages
  • Create switching costs and customer lock-in
  • Invest in brand and customer relationships
  • Monitor startups and disruptors in your space
  • Build alliances and control key resources

Output Process

  1. Assess each of the five forces (High, Medium, Low)
  2. Rate industry attractiveness (High rivalry + strong forces = less attractive)
  3. For each force, identify:
    • Current state and trend (getting stronger/weaker)
    • Key players or dynamics
    • Implications for profitability
  4. Prioritize the 2-3 forces most critical to your strategy
  5. Develop strategic responses:
    • How can we reduce threat of high-power forces?
    • How can we leverage weak forces for advantage?
  6. Identify competitive positioning opportunities
  7. Create strategic initiatives aligned with force analysis

Industry Attractiveness

  • Attractive: Low rivalry, weak supplier/buyer power, few substitutes, high entry barriers
  • Unattractive: High rivalry, strong supplier/buyer power, many substitutes, low entry barriers
  • Moderate: Mixed dynamics requiring strategic differentiation

Notes

  • No industry is universally attractive or unattractive; position matters
  • Same industry can be attractive for some companies, unattractive for others
  • Forces change over time; re-assess as market evolves
  • Use Porter's Five Forces with SWOT and PESTLE for comprehensive analysis
  • Strategy should directly address the highest-force threats

Further Reading

how to use porters-five-forces

How to use porters-five-forces 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 porters-five-forces
2

Execute installation command

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

$npx skills add https://github.com/phuryn/pm-skills --skill porters-five-forces

The skills CLI fetches porters-five-forces from GitHub repository phuryn/pm-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/porters-five-forces

Reload or restart Cursor to activate porters-five-forces. Access the skill through slash commands (e.g., /porters-five-forces) 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.867 reviews
  • Ganesh Mohane· Dec 24, 2024

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

  • Soo Okafor· Dec 24, 2024

    Registry listing for porters-five-forces matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Xiao Torres· Dec 24, 2024

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

  • Xiao Dixit· Dec 8, 2024

    porters-five-forces reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Xiao Flores· Dec 8, 2024

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

  • Lucas Verma· Dec 4, 2024

    Registry listing for porters-five-forces matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sakura Abbas· Nov 27, 2024

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

  • Xiao Rao· Nov 27, 2024

    We added porters-five-forces from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mia Sanchez· Nov 23, 2024

    porters-five-forces is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Camila Khanna· Nov 23, 2024

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

showing 1-10 of 67

1 / 7