# Competitive Research Snapshot

Research a competitive landscape with cited snapshots, a comparison matrix, and so-what...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Writing
- 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-research-snapshot -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-research-snapshot -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-research-snapshot -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill competitive-research-snapshot -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Research 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.

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

# Competitive Research Snapshot

## Purpose

Research a company's competitive landscape using a workflow, not a one-shot answer: **search plan →
competitor selection → just-enough research → fact/inference labels → real URL citations → next-step
options.** The output is a decision-support snapshot, not a market report, and because its schema is
stable, downstream skills (battle cards, delta monitors) can consume it and diff it. Because it
proceeds on labeled assumptions when questions go unanswered, it can run as an agent task or on a
schedule; re-run it and diff against the prior snapshot.

## Input

**Works best with:** the company, product, or segment to research, and **the decision this research
should support** (positioning, roadmap bet, deal support, board prep), the decision determines what
"just enough" means.
**Also useful:** known competitors (or explicit permission to identify them), and any prior snapshot
or `market-landscape-scan` output in session, the skill builds on evidence already gathered rather
than re-researching 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 against the question budget;
don't re-ask.

**Arriving empty-handed? That works too.** The skill opens with at most 3 questions (subject,
decision, competitors) and proceeds on labeled assumptions if they go unanswered.

**Example invocation:** `Competitive research snapshot on our expense-automation product, decision:
which roadmap bet wins Q1. Competitors: [Competitor A], [Competitor B]; find a third if one matters.`

## Key Concepts

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