# Market Landscape Scan

Map a market's segments, players, substitutes, and whitespace with cited evidence.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill market-landscape-scan -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill market-landscape-scan -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill market-landscape-scan -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill market-landscape-scan -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors to study.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 decision.`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/market-landscape-scan/SKILL.md