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 |
assets/heatmap-template.md
View on GitHub# Five Forces Heatmap — Output Template
Include this heatmap inline near the top of `five-forces.md` (after the boundary note, before the per-force assessments). It gives a senior reviewer a 10-second read of where the analysis lands.
## Template
```markdown
## At-a-glance — Force Heatmap
| Force | Intensity | Direction | Velocity | AI reshape | Governs? |
|-------|-----------|-----------|----------|------------|----------|
| Rivalry | Low / Mod / **High** | ↑ / ↔ / ↓ | slow / med / fast | ↑ / ↔ / ↓ / n/a | yes / no |
| Supplier Power | Low / Mod / High | ↑ / ↔ / ↓ | slow / med / fast | ↑ / ↔ / ↓ / n/a | yes / no |
| Buyer Power | Low / Mod / High | ↑ / ↔ / ↓ | slow / med / fast | ↑ / ↔ / ↓ / n/a | yes / no |
| Threat of New Entry | Low / Mod / High | ↑ / ↔ / ↓ | slow / med / fast | ↑ / ↔ / ↓ / n/a | yes / no |
| Threat of Substitutes | Low / Mod / High | ↑ / ↔ / ↓ | slow / med / fast | ↑ / ↔ / ↓ / n/a | yes / no |
| Complementors (6th) | Low / Mod / High | ↑ / ↔ / ↓ | slow / med / fast | ↑ / ↔ / ↓ / n/a | yes / no |
| AI (named force) | Low / Mod / High | ↑ / ↔ / ↓ | slow / med / fast | — | yes / no |
**Governing force:** [name] — see causal sentence below.
```
## Filled exemplar — US ambient-scribe medtech (illustrative)
```markdown
## At-a-glance — Force Heatmap
| Force | Intensity | Direction | Velocity | AI reshape | Governs? |
|-------|-----------|-----------|----------|------------|----------|
| Rivalry | High | ↑ | fast | ↑ | no |
| Supplier Power | Low | ↔ | slow | ↓ | no |
| Buyer Power | High | ↑ | medium | ↑ | candidate |
| Threat of New Entry | High | ↑ | fast | ↑ | **yes** |
| Threat of Substitutes | Moderate | ↑ | medium | ↑ | no |
| Complementors (6th) | High | ↔ | slow | ↔ | candidate |
| AI (named force) | High | ↑ | fast | — | structurally cross-cutting |
**Governing force:** Threat of new entry — AI-native vendors with EHR-app-store distribution achieve clinical-grade product at 1/5 the per-encounter cost basis of legacy transcription incumbents.
```
## Rules for the heatmap
- One word per cell — no prose.
- "Governs?" column has exactly one **yes**; up to two "candidate"; rest "no". If two yes, the analysis hasn't resolved.
- "AI reshape" column for the AI named-force row is "—" (not applicable; covered in the cross-cutting Reshape Matrix lower in the document).
- Velocity column required for any force with direction ≠ stable. Optional but recommended for stable forces.
- The heatmap is a summary, not a substitute — every cell must be backed by the corresponding force section's detailed analysis.
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 |