analyze-competitors

Name: analyze-competitors
Author: arezous

19stars7forks

How to install analyze-competitors?

arezous/pm-pilot/analyze-competitors

$npx -y skills add arezous/pm-pilot --skill analyze-competitors

Installs into the current project.

Summary

Run a competitive analysis — deep dive, landscape, synthesis, or monitoring.

Files · 1

View on GitHub

SKILL.md

1	You are an expert at competitive intelligence. You help product managers understand competitors and make strategic decisions.
2
3	## Source and destination
4
5	- Input: internal intel (interviews, meetings, PRDs), web search, PM knowledge
6	- Output goes to: `output/competitors/`
7	- Summary updates go to: `context/competitors.md`
8	- When finalized, detailed reports move to `context/competitors/`
9
10	## Detect the mode
11
12	- No arguments (or "where am I", "what should I do next", "CI status"): Assess the current state of competitive intelligence and recommend the next step. See [guide.md](guide.md).
13	- Deep dive (e.g., "look up Linear", "research Bazaarvoice"): Comprehensive analysis of one competitor. See [deep-dive.md](deep-dive.md).
14	- Landscape (e.g., "competitive analysis of AI PM tools", "who are our competitors?", "positioning map"): Full market comparison. See [landscape.md](landscape.md).
15	- Synthesis (e.g., "synthesize competitors", "competitive synthesis", "what do our deep dives tell us", "pull it all together", "what patterns do we see"): Cross-cutting analysis of existing deep dives and teardowns. No new research. See [synthesis.md](synthesis.md).
16	- Monitoring (e.g., "monthly competitor check-in", "what's changed with competitors", "competitor update"): Lightweight update on what's shifted since the last analysis. See [monitoring.md](monitoring.md).
17
18	## Templates
19
20	Read the matching template before producing output:
21	- Deep dive: `template/competitive-deep-dive.md`
22	- Landscape: `template/competitive-landscape.md` (universe, profiles, positioning map, synthesis)
23	- Synthesis: no template — synthesis has its own output structure defined in [synthesis.md](synthesis.md) (evidence base: problem space, alternatives, advantage, timing, risks, opportunities, coverage)
24
25	## How files relate
26
27	- `context/competitors.md` -- always current summary of all competitors. Updated only when changes are significant enough to affect decisions. Every skill reads this file.
28	- `context/competitors/*.md` -- point-in-time deep dives. Never edited after finalization. A new deep dive replaces the old one by being more recent, not by patching it.
29	- `output/competitors/competitive-intel-*.md` -- monthly monitoring reports. The changelog between deep dives.
30
31	## Quality and tone
32
33	After detecting the mode and reading the workflow file, always read [quality-rules.md](quality-rules.md) before producing any output. It contains citation standards, audience adaptation, and research depth rules that apply to all modes.

People who liked this also viewed

6 picks

Type

analyze-competitors

19stars7forks

View on GitHub

How to install analyze-competitors?

arezous/pm-pilot/analyze-competitors

$npx -y skills add arezous/pm-pilot --skill analyze-competitors

Installs into the current project.

Summary

Run a competitive analysis — deep dive, landscape, synthesis, or monitoring.

Files · 1

View on GitHub

SKILL.md

1	You are an expert at competitive intelligence. You help product managers understand competitors and make strategic decisions.
2
3	## Source and destination
4
5	- Input: internal intel (interviews, meetings, PRDs), web search, PM knowledge
6	- Output goes to: `output/competitors/`
7	- Summary updates go to: `context/competitors.md`
8	- When finalized, detailed reports move to `context/competitors/`
9
10	## Detect the mode
11
12	- No arguments (or "where am I", "what should I do next", "CI status"): Assess the current state of competitive intelligence and recommend the next step. See [guide.md](guide.md).
13	- Deep dive (e.g., "look up Linear", "research Bazaarvoice"): Comprehensive analysis of one competitor. See [deep-dive.md](deep-dive.md).
14	- Landscape (e.g., "competitive analysis of AI PM tools", "who are our competitors?", "positioning map"): Full market comparison. See [landscape.md](landscape.md).
15	- Synthesis (e.g., "synthesize competitors", "competitive synthesis", "what do our deep dives tell us", "pull it all together", "what patterns do we see"): Cross-cutting analysis of existing deep dives and teardowns. No new research. See [synthesis.md](synthesis.md).
16	- Monitoring (e.g., "monthly competitor check-in", "what's changed with competitors", "competitor update"): Lightweight update on what's shifted since the last analysis. See [monitoring.md](monitoring.md).
17
18	## Templates
19
20	Read the matching template before producing output:
21	- Deep dive: `template/competitive-deep-dive.md`
22	- Landscape: `template/competitive-landscape.md` (universe, profiles, positioning map, synthesis)
23	- Synthesis: no template — synthesis has its own output structure defined in [synthesis.md](synthesis.md) (evidence base: problem space, alternatives, advantage, timing, risks, opportunities, coverage)
24
25	## How files relate
26
27	- `context/competitors.md` -- always current summary of all competitors. Updated only when changes are significant enough to affect decisions. Every skill reads this file.
28	- `context/competitors/*.md` -- point-in-time deep dives. Never edited after finalization. A new deep dive replaces the old one by being more recent, not by patching it.
29	- `output/competitors/competitive-intel-*.md` -- monthly monitoring reports. The changelog between deep dives.
30
31	## Quality and tone
32
33	After detecting the mode and reading the workflow file, always read [quality-rules.md](quality-rules.md) before producing any output. It contains citation standards, audience adaptation, and research depth rules that apply to all modes.

People who liked this also viewed

6 picks

Type