Skip to content

Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/map-five-forces

map-five-forces

Unverified

Produces 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).

FileKindSize
SKILL.mdskill md11.5 KB
assets/heatmap-template.mdmarkdown2.6 KB
evals/evals.jsonconfig5.1 KB
references/ai-as-force.mdmarkdown7.0 KB
references/complementors.mdmarkdown2.4 KB
references/dynamism.mdmarkdown3.8 KB
references/edge-cases.mdmarkdown2.9 KB
references/forces-rubric.mdmarkdown10.5 KB
references/learnings.mdmarkdown2.3 KB
references/platform-extensions.mdmarkdown4.8 KB
scripts/validate_forces.pyexecutablescript8.9 KB

references/dynamism.md

View on GitHub
# Dynamism — Direction of Travel

Five Forces is a snapshot tool. In dynamic environments (BCG Strategy Palette: Adaptive / Shaping / Renewal), a snapshot ages within months and misleads. Every force in `five-forces.md` MUST carry a direction-of-travel arrow over the next 3-5 years.

## Why this matters

A force that is "Low today, intensifying fast" is more strategically important than a force that is "High today, stable." Snapshot intensity tells you where profits sit *now*; trajectory tells you where they will sit when the decision plays out.

## Direction-of-travel categories

| Arrow | Meaning | Decision implication |
|-------|---------|----------------------|
| **Intensifying ↑** | Force will be materially stronger in 3-5yr | Discount future profit pool at this layer; expect margin compression |
| **Stable ↔** | Force structurally locked; no visible mechanism for change | Current profit pool persists |
| **Weakening ↓** | Force will be materially weaker in 3-5yr | Expansion opportunity; expect margin expansion |

## Evidence anchors for each direction

A direction claim, like an intensity claim, requires V/C/A/I-tagged evidence — not vibes.

**Intensifying signals:**
- New entrant funding accelerating (track Series A/B announcement velocity in industry)
- Buyer consolidation in motion (named M&A in last 24 months)
- Substitute price-performance crossing parity threshold
- Regulatory move telegraphed (e.g., FTC consent decree, EU Act proposal)
- AI-driven cost compression actively restructuring incumbents

**Stable signals:**
- HHI changes <5 points over 5 years
- No funded entrants with traction in 3+ years
- Substitute price-performance gap stable or widening in incumbents' favor
- Regulatory regime mature, no proposed changes

**Weakening signals:**
- Failed entrants outnumber funded ones 3:1 over 3 years
- Buyer fragmentation in motion (M&A breakups, new buyer cohorts)
- Substitute category losing share to industry
- Incumbents consolidating profitably (rivalry weakening)
- Regulatory loosening (license caps lifted, etc.)

## Velocity, not just direction

Where possible, qualify the trajectory with velocity:
- **Slow** — material change over 5+ years (regulatory cycles, infrastructure)
- **Medium** — material change in 2-5 years (entrant scale-up, buyer consolidation)
- **Fast** — material change in <2 years (AI cost compression, sudden substitute breakthrough, viral demand-side shift)

Fast trajectories override snapshot intensity in the governing-force decision. A "Moderate, intensifying fast" force often governs even when a "High, stable" force exists alongside it.

## Output requirement

Every force in `five-forces.md` carries a `**Direction:** ↑/↔/↓` line with at least one tagged evidence claim supporting the arrow. The validator (`validate_forces.py`) checks for direction arrows on all six forces (5 classical + complementors) and the AI section.

## Common failure mode

**Symptom:** every force tagged "stable" by default. **Cause:** drafter didn't engage with trajectory; treated direction as box-ticking. **Fix:** if all 7 force-direction arrows say "stable," the analyst hasn't engaged. Real industries always have at least one intensifying or weakening force. The validator warns when all-stable is detected.

## Cross-reference to Strategy Palette

The orchestrator's environment diagnosis (Classical / Adaptive / Visionary / Shaping / Renewal) sets the bar for trajectory rigor:
- **Classical** environment — snapshot dominant; direction is sanity check
- **Adaptive / Shaping / Renewal** — trajectory dominant; snapshot is starting point only
- **Visionary** — snapshot and trajectory both subordinate to the to-be-built future state

If the orchestrator's diagnosis is non-Classical and the Five Forces output has all-stable arrows, the analysis is structurally wrong for the environment. Flag at Gate 2.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall