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/s-curve-methodology.md

View on GitHub
# S-Curve Methodology — Dual Assessment

The industry S-curve frames lifecycle as four stages: **Introduction → Growth → Maturity → Decline**. Modern senior practice requires assessing TWO S-curves in parallel — they desynchronize.

## The two curves

### Market-adoption S-curve
**What it measures:** penetration of the underlying customer need / job-to-be-done by the industry's current solution shape.

| Stage | Penetration | Diagnostic signals |
|------|------------|-------------------|
| Introduction | <5% | Single-digit credible adopters; no dominant design; unit economics unproven or negative; early-adopter customer base; ASP volatile |
| Growth | 5-50% | Dominant design emerging or locked; CAC falling; gross margins improving; share-of-voice rising; capex shifts to volume scaling; copycats arrive |
| Maturity | >50% | Share consolidation; margin compression; capex shifts from growth to defense; pricing pressure; M&A roll-up; private-label or commoditization |
| Decline | Declining absolute volume | Substitution underway; capex zero or negative; profit pool migrates to adjacent layer; rationalization waves |

### Technology S-curve
**What it measures:** capability / cost frontier of the production technology underlying the industry.

| Stage | Cost / capability trajectory | Diagnostic signals |
|------|----------------------------|-------------------|
| Introduction | Cost falling rapidly from high base; capability volatile | Multiple incompatible architectures; performance per $ doubling <2yr; early benchmark wars |
| Growth | Cost continues steady decline; capability plateaus then jumps | Reference architecture stabilizes; tooling/ecosystem builds; talent supply grows |
| Maturity | Cost reductions slow to incremental; capability plateau | Standards bodies dominate; component costs >50% of price; capacity overbuild risk |
| Decline | Successor technology takes share | New S-curve below current cost; incumbent locked in via capex |

## Desynchronization patterns

The two curves rarely sync. Document the relationship explicitly:

- **Market mature + tech early-growth** → tech S-curve will reshape the market S-curve within 5yr (autos pre-EV, banking pre-AI, healthcare pre-genomics)
- **Market growth + tech mature** → commoditization risk; differentiation must come from non-tech factors (brand, distribution, integration)
- **Market early + tech early** → S-curve jump possible; highest discontinuity risk; Counter-Positioning window widest
- **Market mature + tech mature** → Process Power and Branding only remaining Power vectors; H1-heavy portfolio defensible

## Inflection-point detection (the high-value move)

The single most valuable analytical move is detecting the upcoming inflection. Two transitions matter:

1. **Growth → Maturity** — leading indicators: top-5 share movement falling below 5pp over rolling 3yr; CAC stabilization or rise; gross margin peak; capex/revenue declining; M&A roll-up activity rising
2. **Maturity → Decline** — leading indicators: absolute volume flat with population growth (i.e., per-capita declining); successor-tech adoption >5% in adjacent segment; talent migration out

Name the inflection-point indicator you are tracking and its current reading.

## Cycle methodology (when standard S-curve doesn't apply)

For hyper-cycle / sentiment-driven markets — crypto, web3, NFTs, DeFi, blockchain tokens, governance tokens, meme stocks, GameStop-style runs, consumer-LLM hype, and other sentiment-dominated segments — the standard linear S-curve is unreliable. Underlying lifecycle still exists, but it is masked by repeating sentiment cycles of much larger amplitude.

When the validator emits the hyper-cycle warning (or when an industry slug or content body matches keywords like `crypto`, `web3`, `nft`, `defi`, `meme-stock`, `consumer-llm`, `blockchain`, `token`, `governance token`, `gamestop-style`, `sentiment-driven`), switch to **cycle methodology** and capture:

1. **Cycle period in months** — typical peak-to-peak duration (e.g., crypto ~42-48 months; meme-stock ~weeks-to-months).
2. **Amplitude (peak-to-trough %)** — historical drawdown range (e.g., BTC -80% peak-to-trough cycle over cycle).
3. **Dominant sentiment driver** — what moves the cycle (Fed policy / rate regime, regulatory event, viral catalyst, halving event, listing event).
4. **Where in the current cycle the market sits** — accumulation / mark-up / distribution / mark-down (or equivalent), with the leading indicator that confirms the phase.

Then layer the underlying tech S-curve assessment separately. The two analyses serve different decisions: tech S-curve tells you whether the underlying capability is improving; cycle methodology tells you whether to expect a near-term sentiment reversal.

Explicit disclosure in the output (a phrase like "cycle methodology" / "cycle period" / "peak-to-trough" / "sentiment driver") suppresses the validator warning.

## Anti-patterns

- ❌ Single S-curve assessment ("the industry is in growth stage") — ambiguous which curve
- ❌ Copy-paste identical assessment for both curves
- ❌ Stage classification without ≥2 diagnostic signals each tagged
- ❌ "Maturity" claimed without naming the inflection-point indicator that resolves it
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