analyze-competitive-landscape — Claude Code command
analyze-competitive-landscape — a Claude Code command that produces a competitive brief with threat levels, a differentiator map, and a stakeholder-specific action plan.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/analyze-competitive-landscape.mdWhat analyze-competitive-landscape does
The command runs five sequential steps: pulling signals from CRM exports, research feeds, and market news; assigning severity and confidence scores to competitor moves; mapping strengths and weaknesses against each rival; generating counter-plays tailored to the target audience (exec, product, sales, or marketing); then packaging everything into the chosen output format.
Four sub-agents divide the work: market-insights-director drives synthesis and narrative, battlecard-program-manager fills the differentiator map, the market-signal-tracker skill structures signal metadata, and executive-briefing-kit enforces the storytelling format. The final output includes the competitive brief, an action register with owners and due dates, and an appendix of referenced sources.
The optional --signals parameter accepts URLs and files — win/loss exports, deal statistics, third-party research. Without them, the command works from whatever the agent can access in the current session, so the depth of the output depends on what tools are available.
What it helps with
- build a competitive brief for a quarterly business review
- generate battlecards scoped to a specific product segment
- score and rank competitor threats in the enterprise-SaaS segment
- prepare an executive-ready competitive memo before a product launch
- turn raw CRM win/loss exports into a structured action register
Example prompts for the agent
- /competitive-intelligence:analyze-competitive-landscape --scope enterprise-saas --audience exec --window 30d --format deck
- Run a competitive analysis for the mobile segment over the last quarter, audience is product, format memo
- Analyze competitors using
win-loss-q2.csvvia--signalsand produce a sales deck
How to install analyze-competitive-landscape
Manually: put the files in place
.claude/commands/analyze-competitive-landscape.mdCall it with /analyze-competitive-landscape. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/analyze-competitive-landscape.mdCall it with /prompts:analyze-competitive-landscape. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/analyze-competitive-landscape.prompt.mdManually: put the files in place
.gemini/commands/analyze-competitive-landscape.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about analyze-competitive-landscape
How do I install analyze-competitive-landscape in Claude Code?
Place the command file at .claude/commands/analyze-competitive-landscape.md in your project root. Claude Code picks it up automatically from there.
What does the analyze-competitive-landscape command do?
It builds a competitive brief by aggregating market signals, scoring threats, mapping differentiators per competitor, and producing an action register with owners and due dates — formatted as a deck, memo, or document set.
Which parameters does the command accept?
--scope sets the product line or segment, --audience targets exec, product, sales, or marketing, --window sets the time range (30d, 60d, quarter, or custom), and --format picks deck, memo, or docset. --signals is optional and takes external URLs or files such as win/loss exports.
Source text
analyze-competitive-landscape.md · Apache-2.0
--- name: analyze-competitive-landscape description: Produces competitive landscape brief with threat levels, differentiators, and recommended actions. usage: /competitive-intelligence:analyze-competitive-landscape --scope enterprise-saas --audience exec --window 30d --format deck --- # Command: analyze-competitive-landscape ## Inputs - **scope** – product line, segment, or geo focus. - **audience** – exec | product | sales | marketing. - **window** – analysis timeframe (30d, 60d, quarter, custom). - **format** – deck | memo | docset. - **signals** – optional URLs/files to include (research, CRM stats, win/loss exports). ## Workflow 1. **Signal Aggregation** – pull intel from research feeds, CRM, sales notes, and market news. 2. **Threat Assessment** – evaluate competitor moves, assign severity/confidence, link to metrics. 3. **Differentiation Mapping** – highlight core strengths/weaknesses vs each rival. 4. **Action Planning** – recommend counter plays, investments, or messaging pivots per stakeholder. 5. **Executive Packaging** – format narrative, visuals, and action register for the requested format. ## Outputs - Competitive brief (deck/memo) with threat levels, trends, and insights. - Action register with owners, due dates, and success metrics. - Appendix with referenced signals, quotes, and supporting data. ## Agent/Skill Invocations - `market-insights-director` – leads synthesis + executive narrative. - `battlecard-program-manager` – feeds differentiation + plays into the brief. - `market-signal-tracker` skill – structures signals + metadata. - `executive-briefing-kit` skill – enforces storytelling + action format. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents