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/three-horizons.md

View on GitHub
# Three Horizons — Portfolio Overlay

Source: Baghai/Coley/White "The Alchemy of Growth" (1999), updated in McKinsey 2020+ practice (Bradley/Hirt/Smit "Strategy Beyond the Hockey Stick").

## The three horizons

| Horizon | Time frame | Description | Typical resource share (conventional) |
|---------|-----------|------------|--------------------------------------|
| **H1** | 0-2yr | Defend and extend the core. Today's profit engine. Scale economies, efficiency, share defense. | ~70% |
| **H2** | 2-5yr | Build emerging businesses with a proven model. Scaling, not inventing. | ~20% |
| **H3** | 5-10yr | Create viable options. Unproven models, experiments, optionality. | ~10% |

**Modern update (2020+):** In shaping or visionary environments, the allocation flips H3-heavy. Three Horizons is now a portfolio FORCER, not a fixed allocation.

## How to classify a G3 sub-segment

For each G3 sub-segment (from size-market), assess against these criteria:

| Criterion | H1 | H2 | H3 |
|-----------|----|----|-----|
| Business model proven | Yes, decades | Yes, recent | No |
| Unit economics | Positive, predictable | Approaching positive | Negative or unknown |
| Customer adoption | Mainstream | Early majority | Innovators / early adopters |
| Capex character | Maintenance + growth | Growth | Experimentation |
| Time to scale-profit | Now | 2-5yr | 5-10yr |
| Competitor density | High | Moderate | Low / uncategorized |

Sub-segment must satisfy ≥4 criteria for a given horizon. If it spans, split it (the G3 cut was too coarse).

## The bar test

A real industry with >0% aggregate growth ALWAYS has at least one H2 or H3 sub-segment. If every sub-segment classifies H1, one of the following is true:

1. The G3 decomposition was too coarse — re-cut
2. The industry is genuinely declining (no H2/H3) — state this explicitly and note implications for Power Progression (declining-stage Powers only)
3. The drafter underweighted emerging segments — re-scan with broader scope

## Resource allocation implication

After classification, state the implied portfolio allocation as a single sentence:

- "Conventional 70/20/10 applies — industry is balanced, classical environment."
- "Industry warrants 50/30/20 — H3 sub-segment X is the next S-curve and incumbents under-investing."
- "Industry warrants 90/10/0 — Decline-stage, harvest H1 cash, no viable H3 visible."

## Handoff to Power Progression

H3 sub-segments are where Counter-Positioning and Cornered-Resource Powers can be built BEFORE incumbents notice. This is the link to `power-progression.md`: H3 = early-stage Power windows still open; H1 = late-stage Powers only (Scale, Branding, Process).

## Anti-patterns

- ❌ All sub-segments H1 (universal-H1 — fails the bar test)
- ❌ H3 used as "everything I don't understand"
- ❌ No stated resource allocation implication
- ❌ Classification asserted without naming criteria
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