Industry Chain Analysis and Trend Forecasting

Problem context

When analyzing an industry node such as eVTOL flight control systems or solid-state batteries, the hard part is not only collecting sources, but aligning policy, market, and technology evidence into a regional timeline, identifying the stage of development, and estimating where the chain is heading. Adding local enterprises raises another question: which firm belongs to which upstream, midstream, or downstream segment, and which segments are missing in the region.

How it works

The skill takes required industry_node and region, plus optional focus_industry, local_enterprises, and years_back (default 5). It produces a structured Markdown report with:
- Node profile: chain position and key products or technologies.
- Five-year evolution timeline: one or two landmark events per year, including policy releases, market milestones, and technical breakthroughs.
- Dimensional review: policy direction, market-size changes, and core technology iteration, with source notes where available.
- Trend forecast: 3-5 inferential judgments based on technology maturity, policy continuity, and capital flows.
- Enterprise mapping: when local_enterprises is provided, maps firms to chain segments by main business, labels their role, and highlights missing segments.

Limits

It is best for regional industry-node context scans and trend reasoning, not as a real-time database or guaranteed market-data source; when authoritative figures are absent, the report should mark that explicitly. For very new nodes, a default five-year lookback may be too narrow, so the start point should follow the node's actual emergence. Enterprise mapping depends on provided names and business descriptions; firms spanning multiple segments are assigned to their primary segment with a note.