competitive-analysis-process skill
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.
Is the competitive-analysis-process skill safe?
Clean: nothing in its files matched our rules. We read 4 files in the folder on 2026-09-28.
No findings.
Install the competitive-analysis-process skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git /tmp/Product-Manager-Skills mkdir -p ~/.claude/skills cp -r /tmp/Product-Manager-Skills/skills/competitive-analysis-process ~/.claude/skills/competitive-analysis-process
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
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
matrices, positioning moves, threat assessments) are what sales, execs, and roadmap owners actually consume. A step that doesn't feed an output is a detour.
- Six steps, four outputs. The steps are analytical lenses; the outputs (battle cards, comparison
This file holds the sequence, the frameworks, and the decision points — not the research mechanics.
- Steps delegate; this skill orchestrates. Each step below names the skill that does the work.
autonomous-investigation protocol (Fact/Inference/Assumption labels, real URLs, confidence stacking), drawing signals from the channels in intelligence-collection-disciplines.
- Evidence discipline throughout. Every step honors the
the Kano model, Jobs-to-be-Done, the Business Model Canvas, Ries & Trout positioning, Hamel & Prahalad strategic intent. The frameworks are defined where used; agents shouldn't assume prior knowledge.
- Named frameworks, cited. Each step stands on published strategy work — Porter's Five Forces,
and it's the step most teams skip, which is why they're perpetually surprised.
- Present ≠ future. Steps 1-5 read where competitors are; Step 6 reads where they're going —
Application
Step 0 — Scope. Confirm the decision, the competitor set (or run market-landscape-scan to find it), and which steps matter. Offer the six steps as a numbered menu; recommend a subset when the decision doesn't need all six.
Step 1: Overview of the Competitive Landscape
Who's in the game, where, and how they operate — market saturation, fragmentation, disruptive entrants.
competitors by GTM model, innovation pattern, or regional depth); market fragmentation indexing.
- Frameworks: Porter's Five Forces (industry structure); strategic group mapping (clustering
dynamics, whitespace with the dead-zone test.
- Run: market-landscape-scan — segments, player map,
- Decision point: which 2-4 players deserve depth? Everything downstream narrows to them.
Step 2: Comparisons at the Product Level
Beyond feature lists: value delivery, architecture, interoperability, lifecycle maturity.
Product model (core product vs. the ring of services and integrations deals actually hinge on); JTBD-based capability maps (compare by customer job, not by feature name).
- Frameworks: Kano model (which features delight vs. merely satisfy); Geoffrey Moore's Whole
selected players — its comparison matrix is this step's artifact.
- Run: competitive-research-snapshot on the
checklist hides: two "identical" features serving different jobs badly.
- Watch for: feature parity theater. A capability map by job-to-be-done exposes what a feature
Step 3: Ability to Fulfill Customer Needs
How well they serve real customers — outcomes, support quality, ecosystem benefits — not tech specs.
Proposition Canvas (their promise vs. the jobs/pains/gains that matter).
- Frameworks: Outcome-Driven Innovation (score against customer-defined outcomes); Value
buyer reads — need themes, quoted verbatims, competitor weak points, and switching triggers, each with a source-bias note.
- Run: voice-of-customer-miner across the sources your
signal; curated success stories are marketing.
- Watch for: vendor-authored "reviews" and case studies. Independent complaint clusters are the
Step 4: Compilation of Business Information
The financial, organizational, and market baseline: structure, revenue streams, growth levers, channels.
breakdown; sales channel profiling (direct vs. OEM vs. VAR vs. platform).
- Frameworks: Business Model Canvas (how the whole machine fits together); revenue stream
output (financials, offers, org signals) is this step's artifact; FININT sources per intelligence-collection-disciplines do the heavy lifting.
- Run: company-intel per deep-dive competitor — its eleven-section
companies lie less where lying is a felony.
- Watch for: press-release accounting. Filings and earnings calls outrank announcements —
Step 5: Perception and Relative Positioning
How buyers perceive you versus them — in promise, emotion, and mental association, not capability.
mapping (price vs. value-perception plots; find the uncontested space); Blue Ocean strategy canvas.
- Frameworks: Ries & Trout positioning theory (the battle is for the buyer's mind); perceptual
review mining); draft or revise with positioning-statement.
- Run: contrast their stated positioning (Step 2 snapshots) against customer language (Step 3
say they don't cash. That gap is a positioning counter-move waiting to be claimed.
- Watch for: the promise-delivery gap — where a competitor's marketing writes checks their reviews
More skills from deanpeters/Product-Manager-Skills
- Aacquisition-channel-advisorEvaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
- Aagent-orchestration-advisorDesign multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
- Aai-shaped-readiness-advisorAssess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
- Aaltitude-horizon-frameworkUnderstand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
- Aansoff-matrixMap evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.
- Aautonomous-investigationThe protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.
- Abattle-card-builderResearch and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
- Abusiness-health-diagnosticDiagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
- Acompany-intelResearch a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
- Acompany-researchCreate a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
- Acompetitive-intel-watchScheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.
- Acompetitive-research-snapshotResearch a competitive landscape with cited snapshots, a comparison matrix, and so-what implications. Use when a product decision needs competitive grounding, not a market report.