market-landscape-scan

# Market Landscape Scan ## Purpose Map a market's structure using a workflow, not a one-shot answer: **search plan → segmentation → player mapping → dynamics → whitespace → next-step options.** The output is the landscape view that everything downstream stands on — sizing needs to know the segments, positioning needs to know the players, and competitor deep-dives need to know who's worth the effort. This skill maps structure, not magnitude: it tells you who plays where and why, not how big the prize is. ## Input **Works best with:** the market, segment, or problem space to map — in your words, not an analyst category — and **the decision this landscape should support** (market entry, new product line, re-positioning, build-vs-buy). **Also useful:** any boundary narrower than global — geography, buyer size, price band — and players you already know about, so the scan spends its effort on what you don't. Input supplied inline with the invocation — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it against the question budget; don't re-ask. **Arriving empty-handed? That works too.** The skill opens with at most 3 questions (market, decision, boundary) and proceeds on labeled assumptions if they go unanswered — that's the `autonomous-investigation` contract. **Example invocation:** `Run a market landscape scan on developer-facing API observability tools, EU-only — this supports a Q4 market-entry deci...