MCP HubMCP Hub
SKILL·2A4192

porters-five-forces

deanpeters
업데이트됨 6 days ago
5,952
730
5,952
GitHub에서 보기
문서word

정보

이 스킬은 포터의 다섯 가지 힘 모델을 활용해 산업의 경쟁 구조를 분석하며, 각 힘에 대한 근거 기반 평가와 이익 풀을 식별합니다. 개발자가 시장 진입 결정을 객관적으로 평가하거나 마진 감소 원인을 진단할 수 있도록 설계되었습니다. 주요 결과물에는 각 평가를 뒷받침하는 명시적 근거와 해당 산업에서 가치를 누가 획득하고 있는지에 대한 명확한 시각이 포함됩니다.

빠른 설치

Claude Code

추천
기본
npx skills add deanpeters/Product-Manager-Skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/deanpeters/Product-Manager-Skills
Git 클론대체
git clone https://github.com/deanpeters/Product-Manager-Skills.git ~/.claude/skills/porters-five-forces

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Porter's Five Forces (Evidence-Cited)

Purpose

Read an industry's structure through Porter's Five Forces, with evidence: search plan → force-by-force ratings with signals → profit-pool implication → next-step options. Each force — competitive rivalry, threat of new entrants, threat of substitutes, buyer power, supplier power — is rated weak/moderate/strong and justified with documented signals, because a rating without signals is vibes. The analysis closes where it should have been aiming all along: where the profit pool sits and who is squeezing it. Five forces is an argument about where margin goes, not a diagram for slide four.

Input

Works best with: the industry or segment, named as precisely as you can ("clinical data management SaaS," not "healthcare"), and the decision this analysis should support. Also useful: a geographic boundary if the structure differs by region, and a market-landscape-scan in session — the forces read builds on it and searches only gaps.

Input supplied inline with the invocation — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it against the question budget; don't re-ask.

Arriving empty-handed? That works too. The skill opens with at most 3 questions (segment, decision, boundary) and proceeds on labeled assumptions if they go unanswered.

Example invocation: Five forces on mid-market field-service management software, North America — decision: whether we enter or partner.

Key Concepts

  • Governing protocol: honors the autonomous-investigation contract — question budget of 3, search-plan gate, Fact/Inference/Assumption labels, Just Enough Mode (2-4 signals per force), stable schema, 4-option Final Step. Disciplines: FININT (concentration, margins, filings) + OSINT (analyst coverage, trade press) per intelligence-collection-disciplines.
  • The framework (Porter, 1979): industry profitability is determined by five structural forces, not by how hard incumbents work. Rivalry sets the intensity of margin competition; entry threat caps pricing; substitutes cap value; buyer power extracts margin downstream; supplier power extracts it upstream. Structure explains what negotiation skill cannot: pricing power is structural.
  • Ratings must survive "how do you know?" Each weak/moderate/strong rating stands on documented signals — concentration data, switching costs, entry examples and how they fared, substitute adoption curves, margin trends. Forces-with-signals is the difference between naming a framework and using one.
  • AI-driven substitution is a named candidate, always. In most knowledge industries it is now the substitute threat; assess it explicitly in the substitutes force rather than letting the analysis pretend it's 2015. Supplier power gets the same modern read: cloud, model, and platform dependencies are supplier concentration.
  • Industry, not player: this reads what the structure does to everyone who plays. swot-analysis reads one company's position within it.
  • When NOT to use: nascent categories with no stable structure — the forces are still forming; run the landscape scan and revisit.
  • Do-not-invent list: market share, margin data, entrant names, funding rounds, adoption figures.

Application

  1. Credit inline context, then ask only the unanswered questions (max 3):
    1. Which industry or segment, precisely?
    2. What decision should this support?
    3. Any geographic boundary?
  2. Show the 3-bullet search plan — what you'll search per force, source types (filings, analyst coverage, trade press, pricing pages, funding databases), fact/inference separation. Continue unless revised. If a landscape scan is in session, build on it; search only gaps.
  3. Rate each force with signals, then emit the schema below exactly.

Output schema (do not reorder)

# Five Forces: [Industry / Segment]
**As-of date:** | **Boundary:** | **Decision supported:**

## 1. Competitive Rivalry — [weak / moderate / strong]
- Signals: [concentration, growth rate, differentiation, exit barriers — each with URL + label]
- What it means here: [one sentence]

## 2. Threat of New Entrants — [weak / moderate / strong]
- Signals: [entry barriers, capital needs, recent entrants and how they fared, regulation — each with URL + label]
- What it means here: [one sentence]

## 3. Threat of Substitutes — [weak / moderate / strong]
- Signals: [substitute adoption, price-performance trajectory, switching evidence — each with URL + label]
- AI-driven substitution, named and assessed: [labeled]
- What it means here: [one sentence]

## 4. Buyer Power — [weak / moderate / strong]
- Signals: [buyer concentration, switching costs, price transparency, backward-integration examples — URL + label]
- What it means here: [one sentence]

## 5. Supplier Power — [weak / moderate / strong]
- Signals: [supplier concentration (including cloud/model/platform dependencies), input differentiation — URL + label]
- What it means here: [one sentence]

## 6. The Profit Pool (the "so what")
- Where margin sits today, and the force squeezing it: [labeled]
- Structure trend: [tightening / loosening, on what evidence]
- For your decision: [2 sentences tying structure to the decision named above]

### Assumptions to Validate
- [Assumption 1] / [Assumption 2] / [Assumption 3]

A copy/paste fill-in version of this schema, with quality checks, lives in template.md.

Final Step (offer exactly 4 options)

  1. Trace the strongest force into your strategy's exposed assumptions
  2. Run market-landscape-scan to name the players behind each force
  3. Feed the profit-pool read into an Ansoff growth-options analysis (ansoff-matrix)
  4. Schedule-ready version: which force signals should a re-run watch?

Accept 1, 2, 3, 4, 1 and 3, Verbose Mode, or a custom path.

Examples

A rating that survives "how do you know?" (fictional):

4. Buyer Power — strong

  • Signals: top 10 buyers account for ~60% of segment spend — Fact ([trade association data, URL]); three publicized incumbent-to-rival switches in 18 months with no reported penalty — Fact ([press coverage, URLs]); public rate cards make pricing fully transparent — Fact ([vendor pricing pages]); one major buyer built the capability in-house — Fact ([their engineering blog, URL])
  • What it means here: buyers can credibly threaten to leave or build, so list-price integrity is an illusion in this segment — discounting pressure is structural, not a sales-discipline problem.

The profit-pool close doing its job: rivalry moderate, entrants weak, substitutes strong (AI agents absorbing the low-complexity tier), buyers strong, suppliers moderate. The pool sits in the regulated high-complexity tier — the only place two strong forces don't reach — Inference. For the entry decision: enter only via the regulated tier; the volume tier's margin is already spoken for by buyers below and AI substitution above.

See examples/sample.md for a complete worked five-forces read (fictional FSM-software market) that builds on the market-landscape-scan example and lands at a profit-pool close that changes the decision. examples/sample-industrial.md shows the forces inverting in an industrial market — read both to see the framework adapt instead of recite.

Common Pitfalls

  • Ratings as vibes. "Rivalry: strong" because it feels crowded. Every rating stands on signals with URLs, or the whole exercise is a diagram.
  • Skipping the AI substitute. Assessing substitutes as adjacent products while an AI workflow eats the category's low end. Name it and rate it, even when the rating is "weak — for now."
  • Confusing competitors with structure. Listing who plays (that's the landscape scan) instead of what the structure does to everyone who plays. The forces are about margin physics, not rosters.
  • No profit-pool close. Five rated forces and no answer to "where does margin go?" The close is the analysis; everything above it is evidence assembly.
  • Forcing structure onto a nascent category. Rating forces that haven't formed yet produces confident noise. Say "still forming," scan the landscape, revisit in two quarters.

References

  • autonomous-investigation (Workflow) — the governing protocol
  • intelligence-collection-disciplines (Component) — FININT/OSINT sources behind the signals
  • market-landscape-scan (Workflow) — who plays; this skill asks what the structure does to them
  • swot-analysis (Workflow) — one company's position within the structure
  • ansoff-matrix (Workflow) — growth options informed by the profit-pool read
  • Michael E. Porter, "How Competitive Forces Shape Strategy" (Harvard Business Review, 1979)
  • Adapted from market-intelligence/porters-five-forces-prompt.md in the https://github.com/deanpeters/product-manager-prompts repo.

GitHub 저장소

deanpeters/Product-Manager-Skills
경로: skills/porters-five-forces
0
ai-agentsai-product-managementclaude-skillspm-frameworksproduct-management
FAQ

자주 묻는 질문

porters-five-forces Skill이란 무엇인가요?

porters-five-forces은(는) deanpeters이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 porters-five-forces 관련 작업을 수행할 수 있게 합니다.

porters-five-forces은(는) 어떻게 설치하나요?

이 페이지의 설치 명령을 사용하세요. porters-five-forces을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.

porters-five-forces은(는) 어떤 카테고리에 속하나요?

porters-five-forces은(는) 문서 카테고리에 속합니다.

porters-five-forces은(는) 무료로 사용할 수 있나요?

네. porters-five-forces은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.

연관 스킬

railway-docs
문서

이 스킬은 Railway의 기능, 작동 방식 또는 특정 문서 URL에 대한 질문에 답하기 위해 최신 Railway 문서를 가져옵니다. 개발자들이 Railway의 공식 소스로부터 정확하고 최신 정보를 직접 받을 수 있도록 보장합니다. 사용자가 Railway의 작동 방식을 묻거나 Railway 문서를 참조할 때 사용하세요.

스킬 보기
n8n-code-python
문서

이 Claude Skill은 n8n의 Code 노드에서 Python 코드를 작성할 때 전문적인 지침을 제공하며, 특히 Python 표준 라이브러리 사용과 n8n의 특수 구문인 `_input`, `_json`, `_node` 작업에 중점을 둡니다. 이는 개발자가 n8n 내에서 Python의 제한 사항을 이해하도록 돕고, 대부분의 워크플로에는 JavaScript 사용을 권장하면서도 특정 데이터 변환 요구사항에 대한 Python 솔루션을 제안합니다.

스킬 보기
archon
문서

Archon 스킬은 REST API를 통해 RAG 기반 시맨틱 검색과 프로젝트 관리를 제공합니다. 이 스킬을 사용하여 문서 검색, 계층적 프로젝트/태스크 관리, 문서 업로드 기능을 갖춘 지식 검색을 수행할 수 있습니다. 외부 문서를 검색할 때는 다른 소스를 사용하기 전에 항상 Archon을 최우선으로 활용하세요.

스킬 보기
n8n-code-javascript
문서

이 Claude Skill은 n8n의 Code 노드에서 JavaScript 코드 작성에 대한 전문적인 지침을 제공합니다. `$input`/`$json` 변수, HTTP 헬퍼, DateTime 처리와 같은 필수적인 n8n 특정 구문을 다루며 일반적인 오류를 해결합니다. Code 노드에서 사용자 정의 JavaScript 처리가 필요한 n8n 워크플로우를 개발할 때 활용하세요.

스킬 보기