Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/analyze-trajectory
analyze-trajectory
UnverifiedProduces 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.6 KB |
| assets/trajectory-template.md | markdown | 4.1 KB |
| evals/evals.json | config | 4.9 KB |
| references/discontinuities-catalog.md | markdown | 3.6 KB |
| references/edge-cases.md | markdown | 3.0 KB |
| references/learnings.md | markdown | 2.3 KB |
| references/power-progression.md | markdown | 3.7 KB |
| references/s-curve-methodology.md | markdown | 5.2 KB |
| references/scenario-methodology.md | markdown | 4.6 KB |
| references/three-horizons.md | markdown | 2.8 KB |
| scripts/validate_trajectory.pyexecutable | script | 12.6 KB |
references/discontinuities-catalog.md
View on GitHub# Discontinuities Catalog
A **discontinuity** is a non-smooth event or trend that breaks linear extrapolation of the industry trajectory. Three types — scan all three; do not stop at the obvious one.
> Note: Christensen's "disruption" (2015 narrowing) is a SPECIFIC sub-type — low-end or new-market entrant displacing incumbent. Senior practice in 2026 uses broader "discontinuity" language to include regulatory and behavioral shifts that disruption-theory doesn't cover.
## The three types
### 1. Regulatory discontinuities
Policy / standard / permit / mandate shifts that change the cost structure, the allowed activity set, or the competitive boundary.
Examples (2026 active):
- EU AI Act enforcement (Aug 2026 high-risk system requirements)
- Section 174 R&D capitalization unwinding in US tax code
- GLP-1 reclassification or coverage mandate changes
- EU CSRD scope expansions
- FDA 510(k) AI/ML SaMD pathway updates
- State-level PFAS bans cascading to product reformulation
### 2. Technology discontinuities
Capability or cost step-change in an underlying technology that the industry depends on.
Examples (2026 active):
- LLM inference cost falling another 5-10x by 2027
- Battery $/kWh crossing the $80 threshold (EV TCO parity)
- mRNA / cell-therapy manufacturing cost halving
- Ambient compute / on-device LLMs displacing cloud inference
- Quantum-resistant cryptography mandates by 2030
### 3. Behavioral discontinuities
Customer preference or use-pattern shifts that change demand shape, channel mix, or willingness-to-pay.
Examples (2026 active):
- AI-mediated shopping (agentic commerce) shifting category buyer
- GLP-1 demand suppression in snacks/alcohol/QSR
- Return-to-office reversal or entrenchment
- Subscription fatigue → re-bundling
- Gen-Z preference for AI-narrated entertainment
## Timing window methodology
**MANDATORY: explicit year ranges.** "Soon" / "eventually" / "in coming years" fail validation.
Structure each timing window as:
| Discontinuity | Likely window | Possible window | Leading indicator |
|---------------|--------------|-----------------|-------------------|
| [name] | YYYY-YYYY | YYYY-YYYY | [named signal that resolves the window] |
The **leading indicator** is the signal you would track to know whether the window is opening or sliding. Examples:
- For EU AI Act: "first enforcement action against a major US AI provider"
- For battery cost: "Tesla or CATL announcing <$80/kWh cell ASP"
- For agentic commerce: "Shopify or Amazon publishing share of orders placed by agents"
## Direction of impact
Each discontinuity acts on the industry profit pool in one of three ways:
- **Compress** — overall profit pool shrinks (price erosion, cost increase, demand suppression)
- **Expand** — overall profit pool grows (new use cases, regulatory tailwind, demographic shift)
- **Redistribute** — profit migrates between layers or players (intermediary disintermediated, new entrant captures value, layer shifts)
State direction explicitly for each discontinuity.
## How many to identify
≥2 across the three types for a 5yr horizon. Real industries in 2026 typically have 3-5. If your scan returns only one, your scan was incomplete — re-scan all three types deliberately.
## Anti-patterns
- ❌ "AI will disrupt this industry soon" — no type, no window, no leading indicator
- ❌ Only technology discontinuities considered (regulatory and behavioral skipped)
- ❌ Timing window stated as "in the coming years" or "by the end of the decade"
- ❌ Direction of impact not stated (compress vs expand vs redistribute)
- ❌ Leading indicator absent — the discontinuity is unfalsifiable
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 |