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/complementors.md
View on GitHub# Complementors — Sixth Force
Source: Brandenburger & Nalebuff, *Co-opetition* (1996). Reframed by BCG Henderson Institute for platform-era industries.
A **complementor** is a firm or platform whose presence INCREASES the value of this industry's product to its customers. Not a competitor, not a supplier, not a buyer.
## Examples by industry
| Industry | Complementor type | Specific examples |
|----------|-------------------|------------------|
| Mobile gaming | App stores, payment rails | Apple App Store, Google Play, Stripe |
| Electric vehicles | Charging networks, battery suppliers | ChargePoint, Tesla Supercharger, CATL |
| Medtech devices | Certification bodies, hospital IT | FDA, CE Mark, Epic, Cerner |
| Industrial robotics | Software/ML libraries, sensor makers | ROS, NVIDIA Isaac, Cognex |
| Cloud SaaS | CRM/data integrations, marketplaces | Salesforce AppExchange, Snowflake Marketplace |
| Pharma | CROs, regulatory consultancies | IQVIA, Parexel |
## Assessment
For each major complementor category, capture:
1. **Concentration** — is this complementor a monopoly/oligopoly, or fragmented?
2. **Leverage** — can the complementor extract value from the industry (e.g., app-store 30% take, payment rail interchange)?
3. **Direction of travel** — is the complementor's leverage growing, stable, or weakening?
## Output
A section in `five-forces.md` titled "Complementors (Sixth Force)":
```markdown
## Complementors (Sixth Force)
**Intensity:** Low | Moderate | High
**Direction:** intensifying | stable | weakening
| Complementor category | Concentration | Leverage | Direction |
|-----------------------|--------------|----------|-----------|
| [name] | concentrated/fragmented | high/moderate/low | ↑↔↓ |
**Structural reason:** [one sentence on why complementors have this aggregate leverage on this industry]
```
## When complementors matter most
- Platform industries (any with two-sided market dynamics)
- Industries with mandatory certifications/standards
- Industries dependent on a critical input or distribution channel
- Industries where customer adoption requires ecosystem readiness (charging stations, app ecosystems, integration partners)
## When "none material" is acceptable
Some industries genuinely have no material complementors (e.g., bulk commodity chemicals sold direct to industrial buyers). State this explicitly with one-sentence justification — don't just omit the section.
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 |