landscape — Claude Code command: map domain space and players
A Claude Code command that maps a domain landscape: identifies key players, available tools, trends and gaps. Takes a domain name or works in current context without arguments.
MIT ★ 1,988 updated 2026-04-01
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resourcesWhat landscape does
The command asks clarifying questions about scope, focus and depth, then builds a structured map: categories, players per category, trends, gaps and strategic insights. The output includes positioning of opportunities, standard technical approaches in the space, and guidance on what to adopt, monitor or avoid.
It saves the full report to artifacts/research/ with filename YYYY-MM-DD-[topic]-landscape.md. Runs on Claude Code; also available for Codex, GitHub Copilot and Gemini CLI in their respective config formats.
What it helps with
- understand which players operate in a domain and their positions
- identify white space or a niche for entry
- spot trends and where the industry is heading
- learn the standard technical stack used in the space
- plan strategy informed by market landscape analysis
Example prompts for the agent
- Request a map: “/landscape generative AI in coding”
- Map current context: “/landscape” with no arguments while working on a topic
- Answer follow-up questions to refine scope and research goals
How to install landscape
1Plugin marketplace
/plugin marketplace add glittercowboy/taches-cc-resources/plugin install taches-cc-resources@taches-cc-resources2Manually: put the files in place
.claude/commands/landscape.mdCall it with /landscape. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/landscape.mdCall it with /prompts:landscape. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/landscape.prompt.mdManually: put the files in place
.gemini/commands/landscape.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about landscape
How do I install landscape in Claude Code?
Run two commands in order: /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources. The command will be available as /landscape.
What does landscape do?
Maps a domain landscape: categorizes the space, lists key players and tools per category, identifies trends and gaps, saves a report with strategic insights about opportunities and recommendations for standard tech approaches.
Can I use landscape in other IDEs?
Yes. The command is available for Codex (~/.codex/prompts/landscape.md), GitHub Copilot (.github/prompts/landscape.prompt.md) and Gemini CLI (.gemini/commands/landscape.toml).
Source text
landscape.md · MIT
--- description: Map the space - tools, players, trends, gaps in a domain argument-hint: [domain/space or leave blank for current context] --- <objective> Map the landscape of $ARGUMENTS (or the current topic if no arguments provided). Understand the full space: who the players are, what tools exist, where things are heading, and where the gaps are. </objective> <intake_gate> <context_analysis> First, analyze $ARGUMENTS to extract what's already provided: - The domain/space to map - Scope boundaries - Known players or categories - What you're trying to learn Only ask about genuine gaps - don't re-ask what's already stated. </context_analysis> <initial_questions> Use AskUserQuestion to ask 2-4 questions based on actual gaps: **If scope unclear:** - "How broad?" with options: Narrow niche, Specific category, Broad space, Entire industry, Other **If focus unclear:** - "What matters most?" with options: Key players, Available tools, Market trends, Gaps/opportunities, All of the above, Other **If depth unclear:** - "How comprehensive?" with options: Quick overview, Solid map, Exhaustive research, Other **If use unclear:** - "Why do you need this map?" with options: Find opportunities, Understand competition, Choose tools, Strategic planning, Other Skip questions where $ARGUMENTS already provides the answer. </initial_questions> <decision_gate> After receiving answers, use AskUserQuestion: Question: "Ready to map the landscape, or would you like me to ask more questions?" Options: 1. **Start mapping** - I have enough context 2. **Ask more questions** - There are details to clarify 3. **Let me add context** - I want to provide additional information If "Ask more questions" → generate 2-3 contextual follow-ups, then present decision gate again If "Let me add context" → receive input, then present decision gate again If "Start mapping" → proceed to research </decision_gate> </intake_gate> <process> After intake complete: 1. Define the space/domain boundaries 2. Identify categories within the space 3. Map key players and tools per category 4. Identify trends and direction 5. Find gaps and emerging areas 6. Synthesize into strategic understanding </process> <output_format> ## Landscape Map: [Domain/Space] ### Strategic Summary [2-3 sentences: shape of the space, key trend, main opportunity] ### Scope [What's included and excluded from this landscape] ### Categories **[Category 1: e.g., "Data Storage"]** - **Established players:** [Names] - **Emerging players:** [Names] - **Key tools:** [Tools/products] - **Trend:** [Where this category is heading] **[Category 2: e.g., "Processing"]** [Same structure...] **[Category 3: e.g., "Visualization"]** [Same structure...] ### Landscape Map ``` [Visual representation - can be ASCII or description] Category 1 Category 2 Category 3 ----------- ----------- ----------- Player A Player D Player G Player B Player E Player H Player C Player F ``` ### Trends - **[Trend 1]:** [What's happening, implications] - **[Trend 2]:** [What's happening, implications] - **[Trend 3]:** [What's happening, implications] ### Gaps & White Space - **[Gap]:** [Why it's underserved, opportunity size] - **[Gap]:** [Why it's underserved, opportunity size] ### Key Insights 1. [Strategic insight about the space] 2. [Strategic insight about the space] 3. [Strategic insight about the space] ### Implications for Us - [What this means for our strategy/project] - [Where we might fit/compete/differentiate] ### Implementation Context <claude_context> <positioning> - opportunities: [where we could enter/compete] - crowded: [areas to avoid unless differentiating significantly] - emerging: [nascent areas with potential] </positioning> <technical> - standard_stack: [common technical approaches in this space] - integrations: [expected integrations/compatibility] - tools_to_evaluate: [specific tools worth investigating] </technical> <trends> - adopt: [trends to align with] - watch: [trends to monitor] - avoid: [declining approaches] </trends> </claude_context> **Next Action:** Deep dive on specific area, competitive research on key players, or run /plan/brief to define our approach ### Sources - [Source name]: [URL] - [date accessed] - [Source name]: [URL] - [date accessed] </output_format> <artifact_output> Save the research to a file: 1. Create directory structure if it doesn't exist: - `[current-working-directory]/artifacts/research/` 2. Generate filename from topic: - Get current date in YYYY-MM-DD format - Slugify the topic (lowercase, hyphens for spaces) - Format: `YYYY-MM-DD-[topic]-landscape.md` - Example: `2025-01-15-music-production-tools-landscape.md` 3. Write the complete research to the file 4. Report to user: "Saved to `artifacts/research/[filename]`" </artifact_output> <success_criteria> - Categories are mutually exclusive and collectively exhaustive - Players are correctly positioned - Trends are backed by evidence - Gaps are genuine opportunities (not just missing features) - Implementation context gives Claude strategic and technical direction - Provides strategic clarity about the space - Output saved to artifacts/research/ directory </success_criteria>
© Lex Christopherson · MIT · glittercowboy/taches-cc-resources