borghei/Claude-Skills / project-management/strategy-frameworks/porters-five-forces
porters-five-forces
VerifiedRates the five competitive forces of one precisely defined industry with evidence and turns the dominant forces into moves. Use when weighing market entry, diagnosing margin pressure or auditing industry positioning.
Porter's Five Forces
Michael Porter's framework for analyzing the structural attractiveness of an industry. Reveals where profit pools form, why some markets are chronically unprofitable, and where strategic positioning has leverage.
Done looks like: an industry named by segment and geography; each force rated low, medium or high with at least two factors and cited evidence; the one or two dominant forces named; 2-3 high-priority moves that counter them; five_forces_scorer.py exits 0.
When to Use
- A market-entry or M&A decision that turns on industry attractiveness
- Margins keep falling and nobody can say which force moved
- Planning a defensive strategy or competitive response
Firm-level strengths and weaknesses belong in swot-analysis; the forces, their sub-factors and examples are in references/five-forces-deep.md (the complementors "sixth force" is optional).
Clarify First
Before scoring the forces, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Precise industry definition: narrow enough to be specific, broad enough to catch substitutes (too broad/narrow is the #1 error and sets the entire analysis scope).
- Evidence per force: the data/facts behind each low/medium/high rating (a score without evidence is just opinion).
- Purpose: market entry / margin-pressure diagnosis / positioning audit (frames which dominant force matters and the strategy translation; margin diagnosis also needs a then-vs-now comparison).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
Quick Start
# Sound analysis: two dominant forces, three moves, exit 0
python3 project-management/strategy-frameworks/porters-five-forces/scripts/five_forces_scorer.py \
--input project-management/strategy-frameworks/porters-five-forces/assets/sample_forces.json --format markdown
# "Software", a missing force and an invalid rating: exit 1
python3 project-management/strategy-frameworks/porters-five-forces/scripts/five_forces_scorer.py \
--input project-management/strategy-frameworks/porters-five-forces/assets/sample_forces_flawed.json --format markdown
# Input schema and flags
python3 project-management/strategy-frameworks/porters-five-forces/scripts/five_forces_scorer.py --help
Tools Overview
five_forces_scorer.py is the quality gate for this skill. What the scorer checks: an industry definition of useful length; all five forces rated with a valid intensity (fail otherwise); at least two factors and some evidence per force; all-medium ratings; strategy implications present with 1-5 high-priority moves. It sums intensities (low 1, medium 2, high 3) into an attractiveness band and reports "Not rated" while any force is missing. It does not judge whether the factors or evidence are right.
Exit codes: 0 no fail findings · 1 at least one fail (missing industry, an unscored force, an invalid intensity) · 2 unreadable file, invalid JSON or a top level that is not an object. JSON by default, --format markdown, --output FILE.
Workflow
- Define the industry by segment, buyer and geography. "Software" and "B2B SaaS" are too broad; "mid-market HR analytics SaaS in North America" works. Too narrow misses substitutes.
- Rate each force low, medium or high using the sub-factors in
references/five-forces-deep.md, with at least two factors and the evidence behind them. Rating everything medium usually means the factors were not weighed. - Name the dominant forces (usually one or two): they set the profit pool.
- Translate to moves. For each high force, pick the counter from
references/five-forces-and-strategy.md(barriers, diversifying supply or buyers, defending the value proposition, niching or consolidating) and mark 2-3 as high priority. For margin diagnosis, rate the industry then and now and name the force that shifted. - Audit. Write the analysis as JSON (schema in
--help;assets/sample_forces.jsonis a complete example) and run the scorer.
Anti-Patterns
The industry is "software"
Mistake: The industry is defined so broadly that every force is "it depends". Why it happens: A broad label feels safe and avoids choosing a segment. Instead: Name segment, buyer and geography; check that the substitutes you care about still fall inside.
Ratings without evidence
Mistake: Each force gets a colour and no factors or data. Why it happens: The ratings feel obvious to people inside the industry. Instead: Two factors and one piece of evidence per force; the scorer warns when either is missing.
Scores with no moves
Mistake: The analysis ends at "unattractive, 12/15". Why it happens: The scoring feels like the work. Instead: Turn each dominant force into a move with an owner, and refresh the analysis every 12-18 months.
Scope & Limitations
In Scope:
- Industry analysis across Porter's five forces: new entrants, supplier power, buyer power, substitutes and competitive rivalry, plus complementors as an optional sixth force
- A low, medium or high rating per force from a factor rubric, with evidence
- Identifying the one or two dominant forces and translating each high force into strategic moves
- A scorer that flags unscored forces, thin factors, missing evidence, all-medium ratings and absent strategy implications (
five_forces_scorer.py) - Market entry, margin pressure and strategic position engagements
Out of Scope:
- Firm-level strengths and weaknesses (see
project-management/strategy-frameworks/swot-analysis/) - Choosing among growth bets (see
project-management/strategy-frameworks/ansoff-matrix/) - Teardowns of individual competitors (see
business-growth/competitive-teardown/) - Market sizing and primary market research (see
research-ops/market-research/)
Important Caveats:
five_forces_scorer.pyreads a hand-written JSON file. Intensity ratings, factors and evidence come from the user, and the tool pulls in no market data.- The analysis is only as sound as the industry definition. Too broad gives generic results, and too narrow misses substitutes.
- Ratings are judgments. Without cited evidence they are opinion.
- Industries change. The skill recommends a refresh every 12-18 months.
Files
| File | Purpose |
|---|---|
scripts/five_forces_scorer.py | Five Forces audit and attractiveness band |
assets/sample_forces.json | HR analytics SaaS analysis; exits 0 |
assets/sample_forces_flawed.json | Broad industry, missing force, invalid rating; exits 1 |
assets/five_forces_template.md | Fill-in template |
Reference Documentation
- references/five-forces-deep.md: Each force, sub-factors, examples
- references/five-forces-and-strategy.md: Translating forces into strategic moves
Related skills
project-management/strategy-frameworks/swot-analysis— firm-level positioningproject-management/strategy-frameworks/ansoff-matrix— growth optionsproject-management/strategy-frameworks/business-model-canvas— operational viewbusiness-growth/competitive-teardown— competitor-specific analysisc-level-advisor/ceo-advisor— strategic context
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |