Competitor Intelligence & Feature Comparison Matrix

What it does

/competitive-analysis is a Cursor slash command. Type it in chat to run a saved workflow: Competitor Intelligence & Feature Comparison Matrix.

Analyzes competitor feature sets, pricing tiers, weaknesses, and market opportunities, creating head-to-head comparison battlecards and landing copy.

Feature parity audits, pricing teardowns, and 'Alternative To' battlecards. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /competitive-analysis for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /competitive-analysis exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Market & Competitor Analyst (competitive-analyst) and Product Positioning Expert (positioning-strategist) agents. Required skills: Competitor Analysis & Feature Differentiation Matrix; April Dunford Product Positioning Framework.

When to use it

• Use when creating comparison landing pages or evaluating market positioning.
• Use /competitive-analysis when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /competitive-analysis as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Audit competitor feature sets, pricing models, and licensing terms
2. Construct objective comparison matrix highlighting key differentiators
3. Draft 'Why Choose Us' bullet points and objection-handling copy
4. Auto-save battlecard to docs/marketing/competitor-matrix.md

Example usage

Type this in Cursor chat: /competitive-analysis Build comparison feature matrix vs traditional boilerplates and kits

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/competitor-matrix.md

Best practices

• Keep the prompt specific. /competitive-analysis Build comparison feature matrix vs traditional boilerplates and kits is the shape: object, constraint, and outcome.
• Let the listed agents work in order: competitive-analyst → positioning-strategist.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /competitive-analysis with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Competitor Analysis & Feature Differentiation Matrix skill that the command depends on.