competitive-research
Competitive Research
Conduct systematic competitive research using the competitor-researcher agent. Analyzes each competitor thoroughly and synthesizes findings into actionable insights.
Inspired by Teresa Torres' workflow for systematic competitive intelligence.
Entry Point
When this skill is invoked, start with:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
COMPETITIVE RESEARCH
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Systematic competitive intelligence that compounds over time.
What competitors do you want to analyze?
(Names or URLs)
What's your focus?
• Pricing
• AI features
• UX/product experience
• Go-to-market
• All of the above
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Usage
/competitive-research
Then provide:
- Competitors to analyze (names or URLs)
- Focus areas (pricing, AI features, UX, etc.)
What Happens
- Gathers input - Which competitors? What focus?
- Researches sequentially - Each competitor analyzed thoroughly (10-15 min each)
- Saves individual files - One markdown file per competitor
- Synthesizes findings - Comparison tables and strategic recommendations
- Creates Linear issue (optional) - Track insights in your workflow
First-Time Setup
On first run, you'll be asked where to save research:
Where should I save competitive research files?
Recommendation: Create a directory OUTSIDE your company codebase, like:
- ~/Documents/pm-work/competitive-research
- ~/pm-research
- ~/competitive-intel
This keeps sensitive competitive analysis separate from your company's git repos.
The Compound Effect
This is your FIRST analysis - thorough and time-consuming. Next time you update this research? Minutes, not hours. That's how systems compound.
| Analysis Round | Time | What Happens |
|---|---|---|
| First | 1 hour | Thorough, structured research |
| Second | 15 min | Update existing files |
| Third | 15 min | Compare to previous versions |
Output Structure
[research-dir]/
└── YYYY-MM-DD-[topic]/
├── competitor-1.md # Individual analysis
├── competitor-2.md # Individual analysis
├── competitor-3.md # Individual analysis
└── synthesis.md # Comparison & recommendations
Synthesis Contents
The synthesis file includes:
- Executive Summary - What did you learn?
- Strategic Positioning Comparison - How competitors position
- Feature/Capability Comparison - Side-by-side table
- Pricing Comparison - Models and tiers
- Strategic Gaps & Opportunities - Where can we win?
- Recommended Actions - Now, next, later
Linear Integration (Optional)
If Linear MCP is configured:
- Creates issue with executive summary
- Links to research files
- Highlights top 3 recommended actions
- Labels with "competitive-intel"
Related Commands
/strategy-session "competitive positioning"- Discuss findings strategically
Philosophy (Teresa Torres):
- Sequential reliability - Process one competitor at a time
- Compounding system - First analysis is thorough, updates are fast
- Data ownership - Everything stored locally
- Synthesis matters - Raw research isn't useful without insights
More from breethomas/pm-thought-partner
agent-workflow
Expert system for designing and architecting AI agent workflows based on proven Meta methodologies. Use when users need to build AI agents, create agent workflows, solve problems using agentic systems, integrate multiple tools into agent architectures, or need guidance on agent design patterns. Helps translate business problems into structured agent solutions with clear scope, tool integration, and multi-layer architecture planning.
9context-engineering
[ARCHIVED] Full 4D Context Canvas reference. For new AI features, use /spec --ai. For debugging, use /ai-debug. For quality checks, use /context-check.
6spec
Write specifications at the right depth for any project. Progressive disclosure from quick Linear issues to full AI feature specs. Embeds Linear Method philosophy (brevity, clarity, momentum) with context engineering for AI features. Use for any spec work - quick tasks, features, or AI products.
2pmf-survey
Create and analyze a PMF survey using Rahul Vohra's Superhuman framework. The magic 40% benchmark for product-market fit.
2four-risks
Run Marty Cagan's Four Risks assessment on an issue (value, usability, feasibility, viability). Use when evaluating features before building.
2strategy-session
Your product soundboard. Work through product decisions conversationally - Claude gathers context, challenges assumptions, captures decisions, and creates Linear issues.
2