Skip to content

Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/analyze-trajectory

analyze-trajectory

Unverified

Produces a forward-looking industry trajectory analysis: dual S-curve (market-adoption + technology lifecycle with diagnostic signals), Three Horizons overlay on G3 sub-segments (consumes size-market when present), discontinuities catalog (regulatory/tech/behavioral with year-range timing windows), Helmer Power Progression (which 7 Powers are buildable now / Year 3 / Year 5 / closed), and base/bear/bull scenarios with ≥3 named swing variables for the 5-year horizon. Output: trajectory.md with V/C/A/I tags. Sub-skill of analyze-industry but invocable standalone. Triggers on 'industry trajectory for [industry]', 'where is [industry] on the S-curve', 'three horizons for [industry]', 'scenario analysis for [industry]', 'discontinuities facing [industry]'. Do NOT activate for company-specific moat assessment (use assess-moat-sources), market sizing (use size-market), or competitive arena mapping (use map-competitive-arena).

references/power-progression.md

View on GitHub
# Helmer's Power Progression

Source: Hamilton Helmer, "7 Powers" (2016), Chapter 10 — Power Progression. Maps which of the 7 Powers can be acquired at which lifecycle stage.

## The 7 Powers (reminder)

1. **Scale Economies** — unit cost declines with volume
2. **Network Economies** — value to user increases with other users on the platform
3. **Counter-Positioning** — incumbent cannot mimic the new model without cannibalizing existing profits
4. **Switching Costs** — customer cost (financial, procedural, relational) to switch suppliers
5. **Branding** — durable preference premium attributable to identity, accumulated over decades
6. **Cornered Resource** — preferential access to a coveted asset (talent, deposit, IP, license)
7. **Process Power** — embedded organizational processes/culture that competitors cannot replicate quickly

## Power Progression — windows by lifecycle stage

The central insight: **Powers have time-windows.** Late entrants to a mature industry CANNOT build Counter-Positioning or Cornered Resource — those windows shut.

| Power | Origination (Intro → early Growth) | Take-off (Growth) | Stable (Maturity) | Decline |
|-------|-----------------------------------|-------------------|-------------------|---------|
| Counter-Positioning | **OPEN** (best window) | Closing | **CLOSED** | CLOSED |
| Cornered Resource | **OPEN** (best window) | Closing | **CLOSED** | CLOSED |
| Scale Economies | Building | **OPEN** (best window) | Locked-in (defense only) | Defense |
| Network Economies | Building | **OPEN** (best window) | Locked-in (defense only) | Defense |
| Switching Costs | Building | **OPEN** (build via install-base lock) | Reinforce | Defense |
| Branding | Cannot — too early | Building (slow) | **OPEN** (accumulates) | Defense |
| Process Power | Cannot — too early | Building (slow) | **OPEN** (accumulates) | Defense |

## How to use this for trajectory work

Given the lifecycle stage from `s-curve-methodology.md` (use the EARLIER of the two S-curves as the binding constraint — if market is mature but tech is early-growth, Powers tied to tech are still openable):

1. List all 7 Powers
2. For each, mark the state as one of:
   - **Open now** — buildable today
   - **Open Year 3** — window opens as the industry transitions (often: tech S-curve catches up)
   - **Open Year 5+** — long-dated, accumulates slowly (Branding, Process Power)
   - **Closed** — window shut

3. Hand off the table to `assess-moat-sources` — that skill picks WHICH Powers a specific firm should pursue. This skill establishes the menu.

## Worked example

US ambient-scribe medtech (mid-2026, focal layer: vendor):
- Market S-curve: early Growth (~10-15% penetration)
- Tech S-curve: Growth (LLMs stable but cost falling 5x/yr)
- Binding constraint: early-Growth

Powers:
- Counter-Positioning: **Open now** (incumbents like Epic/Cerner can't mimic standalone scribe without cannibalizing EHR module revenue)
- Cornered Resource: **Open now** (training-data partnerships with health systems; closing as data deals get signed)
- Scale Economies: **Open Year 3** (need volume to amortize model training)
- Network Economies: **Closed (likely)** (no inter-doc network value)
- Switching Costs: **Open Year 3** (workflow integration deepens)
- Branding: **Open Year 5+** (clinician trust takes years)
- Process Power: **Open Year 5+** (sales/deployment motion)

## Anti-patterns

- ❌ Asserting all 7 Powers as "available" — Power Progression is precisely about which windows shut
- ❌ Recommending Counter-Positioning strategy for a 30-year-old mature industry
- ❌ Promising Branding inside a 2yr window — Branding accumulates over decades
- ❌ Skipping the table entirely — Power Progression is the skill's central trajectory-to-strategy bridge
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