# Competitive Analysis Process

Orchestrate a complete competitive analysis across six steps, from landscape to...

- 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 competitive-analysis-process -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-analysis-process -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-analysis-process -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-analysis-process -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.

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

# Competitive Analysis Process

## Purpose

Orchestrate rigorous, repeatable competitive analysis across **six analytical steps**, producing four
actionable output types (battle cards, comparison matrices, positioning counter-moves, threat
assessments). This is the umbrella: each step names its purpose, its frameworks, and the skill that
does the work, the way `discovery-process` orchestrates the discovery skills. Run all six for a
strategy cycle; run one when a specific question walks in the door. The steps build on each other, but
the sequence bends to the decision.

## Input

**Works best with:** the market or competitor set in scope, and **the decision this analysis
supports**, a roadmap bet, a positioning refresh, a market entry, deal defense. The decision
determines which steps get depth and which get a pass.
**Also useful:** any existing intelligence, a prior landscape scan, snapshots, battle cards, or
`company-intel` output, so steps consume rather than repeat it.

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; don't re-ask.

**Arriving empty-handed? That works too.** The workflow opens by asking what decision is on the table
and what you already know, then recommends which steps to run and in what order.

**Example invocation:** `Run the competitive analysis process on the mid-market payroll space, decision: whether we defend down-market or push up. We have last quarter's landscape scan.`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/competitive-analysis-process/SKILL.md