Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/map-five-forces
map-five-forces
UnverifiedProduces a Porter Five Forces analysis extended with complementors (sixth force, Brandenburger/Nalebuff) and AI-as-named-force (cost-structure impact + new-entry vector + data-intermediary position) for a defined industry. Output: five-forces.md naming THE governing force that determines this industry's profit distribution in one causal sentence, plus per-force intensity assessment with V/C/A/I-tagged evidence and explicit profit-pool cross-reference. Sub-skill of analyze-industry but invocable standalone. Triggers on 'five forces analysis for [industry]', 'Porter analysis for [industry]', 'industry-structure analysis for [industry]', 'is [industry] structurally attractive'. Do NOT activate for single-company competitive positioning (use map-competitive-arena or build-company-model), market sizing (use size-market), or moat assessment of a specific company (use assess-moat-sources).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| assets/heatmap-template.md | markdown | 2.6 KB |
| evals/evals.json | config | 5.1 KB |
| references/ai-as-force.md | markdown | 7.0 KB |
| references/complementors.md | markdown | 2.4 KB |
| references/dynamism.md | markdown | 3.8 KB |
| references/edge-cases.md | markdown | 2.9 KB |
| references/forces-rubric.md | markdown | 10.5 KB |
| references/learnings.md | markdown | 2.3 KB |
| references/platform-extensions.md | markdown | 4.8 KB |
| scripts/validate_forces.pyexecutable | script | 8.9 KB |
references/platform-extensions.md
View on GitHub# Platform Extensions to Five Forces
For platform-ecosystem industries, the classical five-force boundaries (supplier / buyer / competitor / complementor) **shift in months, not years**. Iansiti/Levien call the central firm a "keystone"; Gawer/Cusumano formalize the orchestrator role. Porter himself acknowledged in his 2024 retrospective that complementors should have been the sixth force from the start.
This reference covers what to do differently when the focal industry is platform-structured.
## How to detect a platform industry
Apply this test in step 1 (Intake). If ≥2 are true, the industry is platform-structured and the rest of this reference applies.
1. **Two-sided (or n-sided) market** — value increases for one side as the other side grows (Uber riders ↔ drivers; Visa cardholders ↔ merchants)
2. **Keystone firm** present — one or two firms orchestrate the ecosystem and capture disproportionate value (Apple in mobile, AWS in cloud)
3. **Boundary fluidity** — same actor is supplier today / competitor tomorrow / complementor next quarter (Amazon as marketplace + private-label)
4. **Switching cost mediated by ecosystem** — switching is costly not because of the product but because of the surrounding apps, integrations, data
5. **Network economies** are the dominant durable power (one of Helmer's 7 Powers)
## What changes in the force assessment
### Boundary specification (mandatory)
Add a **"Boundary note"** sub-section to the front of `five-forces.md` for platform industries. Specify:
- Who is the keystone? (the orchestrator, possibly more than one)
- Which actors are "in" the ecosystem vs adjacent?
- Which actors play multiple roles (supplier + competitor)?
- Which boundaries are stable vs shifting?
Without this, the force assessments are arguing about different definitions.
### Rivalry — assess at TWO levels
1. **Within-ecosystem rivalry** — competition among participants on the same platform (apps competing in App Store)
2. **Cross-ecosystem rivalry** — keystone-vs-keystone competition (iOS vs Android, AWS vs Azure)
A force assessment that only covers one level misses the structural dynamic.
### Supplier Power — the keystone tax
On platforms, the keystone is often the *de facto* supplier of distribution. The App Store 30% take, the AWS infrastructure markup, the Shopify rev-share — these are supplier-power phenomena even though the keystone is officially a "platform."
### Buyer Power — disaggregated
Buyer power on platforms splits into:
- End-user buyer power (often weak — fragmented)
- Keystone buyer power (often very strong — the platform controls discovery, ranking, promotion)
A platform-industry analysis that treats "buyers" as a single class will miss the keystone-side power capture.
### Threat of New Entry — ecosystem barrier
On a platform, the entry barrier is the **complementor ecosystem readiness**, not the product itself. A new mobile OS without an app catalog cannot enter regardless of product quality. This shifts the entry assessment from product-economics to ecosystem-economics.
### Threat of Substitutes — cross-ecosystem
On platforms, substitutes come from adjacent ecosystems (TikTok substitutes for YouTube + Instagram; Discord substitutes for Slack + IRC + voice chat). Substitute analysis must scan adjacent ecosystems, not just within-category alternatives.
### Complementors — the dominant force
For platform industries, complementors are often THE governing force. The structural reason: the platform's value to end users is a function of complementor breadth and quality. If complementors defect (Epic vs Apple over Fortnite), the platform's core value proposition cracks.
### AI as transforming overlay (platform-specific)
On platforms, AI most acutely affects:
- **Discovery / recommendation** — the keystone's central capability — is now AI-mediated
- **Complementor displacement** — generative AI displaces app categories wholesale (image-editing apps vs in-OS generation)
- **Cross-platform substitution** — AI agents shopping across ecosystems collapse keystone lock-in
## Heuristic: when complementors govern
In platform industries, the governing-force sentence often takes this shape:
> "Complementor density governs this industry because the keystone's value to end users is a direct function of [app/integration/partner] catalog breadth, and the top three keystones differ by less than [X]% on baseline product attributes."
If the analysis of a platform industry does NOT name complementors as a serious candidate for governing force, recheck whether the boundaries were correctly specified in the boundary note.
## When this reference does NOT apply
Genuinely non-platform industries — bulk chemicals, cement, primary metals, oil refining, most B2B services — use the classical five-force template without modification. Forcing platform thinking onto a non-platform industry produces nonsense.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |