porters-five-forces
Porter's Five Forces is a strategic framework skill that evaluates competitive intensity across five dimensions: competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants. Use this skill when analyzing industry attractiveness, developing competitive strategies, assessing market entry feasibility, or understanding structural profitability drivers within a specific industry or market segment.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/porters-five-forces && cp -r /tmp/porters-five-forces/pm-product-strategy/skills/porters-five-forces ~/.claude/skills/porters-five-forcesSKILL.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 o
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.