Agent skill

competitive-research

Systematic competitive intelligence with parallel agent analysis. Analyzes competitors thoroughly and synthesizes into actionable insights.

Stars 13
Forks 2

Install this agent skill to your Project

npx add-skill https://github.com/breethomas/bette-think/tree/main/plugins/bette-think/skills/competitive-research

SKILL.md

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

  1. Gathers input - Which competitors? What focus?
  2. Researches sequentially - Each competitor analyzed thoroughly (10-15 min each)
  3. Saves individual files - One markdown file per competitor
  4. Synthesizes findings - Comparison tables and strategic recommendations
  5. 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

Expand your agent's capabilities with these related and highly-rated skills.

breethomas/bette-think

four-fits

Find which fit is broken before you burn cash scaling. Brian Balfour's framework for validating sustainable growth readiness.

13 2
Explore
breethomas/bette-think

project-health

Deep-dive health check on a single Linear project. Produces assessment with 7 dimensions - On Track / At Risk / Stalled.

13 2
Explore
breethomas/bette-think

prompt-engineering

Expert prompt optimization system for building production-ready AI features. Use when users request help improving prompts, want to create system prompts, need prompt review/critique, ask for prompt optimization strategies, want to analyze prompt effectiveness, mention prompt engineering best practices, request prompt templates, or need guidance on structuring AI instructions. Also use when users provide prompts and want suggestions for improvement.

13 2
Explore
breethomas/bette-think

strategy-session

Your product soundboard. Work through product decisions conversationally - Claude gathers context, challenges assumptions, captures decisions, and creates Linear issues.

13 2
Explore
breethomas/bette-think

ai-debug

Diagnose why an AI feature is underperforming, hallucinating, or behaving inconsistently. Uses 4D audit to work backwards from symptoms to root cause.

13 2
Explore
breethomas/bette-think

shape-up

Shape work using the Shape Up methodology (Ryan Singer, Basecamp). Walk through the 4-step shaping process to create pitches ready for betting. Distinguishes between established product mode (fixed time, variable scope) and new product mode (looser constraints). Use when planning cycle work, writing pitches, or coaching PMs on shaping.

13 2
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results