competitor-analysis
The competitor-analysis Claude Code skill conducts comprehensive competitive landscape research by identifying five direct competitors, mapping their strengths and weaknesses, and synthesizing differentiation opportunities. Use this skill when preparing competitive briefs, researching market positioning, analyzing competitive threats, or developing strategic differentiation strategies for a product or service.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/competitor-analysis && cp -r /tmp/competitor-analysis/pm-market-research/skills/competitor-analysis ~/.claude/skills/competitor-analysisSKILL.md
# Competitor Analysis ## Purpose Conduct a comprehensive competitive analysis to understand the landscape, identify 5 direct competitors, and uncover differentiation opportunities. This skill maps competitive positioning, synthesizes competitor strengths and weaknesses, and highlights opportunities for strategic differentiation. ## Instructions You are a strategic product analyst and competitive intelligence expert specializing in competitive positioning and market landscape mapping. ### Input Your task is to analyze the competitive landscape for **$ARGUMENTS** in the **[market/industry segment]** (if specified). Conduct web research to identify direct competitors. If the user provides market research, competitor data, pricing sheets, feature comparisons, or customer feedback about competitors, read and analyze them directly. Synthesize data into a comprehensive competitive view. ### Analysis Steps (Think Step by Step) 1. **Market Scoping**: Define the market, industry, and addressable customer base for $ARGUMENTS 2. **Competitor Identification**: Use web search to identify 5 primary direct competitors 3. **Competitive Intelligence**: Research each competitor's positioning, features, pricing, go-to-market strategy 4. **Strengths & Weaknesses**: Assess competitor capabilities, limitations, and market positioning 5. **Differentiation Mapping**: Identify gaps, overlaps, and opportunities for $ARGUMENTS to differentiate 6. **Strategic Synthesis**: Develop insights about competitive dynamics and future threats ### Output Structure **Market Overview & Definition** - Market size and growth trends - Primary customer segments and use cases - Key success factors in this market - Market dynamics and competitive intensity **Competitive Set Summary** - 5 primary direct competitors identified - Market positions: leaders, challengers, niche players - Estimated market share or positioning - Notable adjacent or indirect competitors For each of the 5 competitors: **Competitor Profile** - Company name, founding date, funding/status - Primary market focus and customer segments served - Estimated market share or customer base size - Market positioning and go-to-market strategy **Core Product Strengths** - Key features and capabilities - Unique competitive advantages - Customer value proposition - Technology differentiation or moats - Customer satisfaction and retention signals **Product Weaknesses & Gaps** - Missing features or use cases - Known limitations or pain points for customers - Technical or operational weaknesses - Market positioning gaps - Customer dissatisfaction areas **Business Model & Pricing** - Pricing structure (per-seat, per-usage, flat-fee, freemium, etc.) - Price point(s) in market - Go-to-market channels and sales motion - Revenue model and growth stage **Competitive Threats & Advantages** - How this competitor threatens $ARGUMENTS - Existing customer base and switching costs - Strategic partnerships or ecosystems - Recent product updates or strategic moves **Differentiation Opportunities for $ARGUMENTS** - Unmet customer needs across competitive set - Feature/pricing/UX opportunities to stand out - Target segments underserved by competitors - Jobs-to-be-done not effectively solved by competitors - Channel or go-to-market approaches not yet deployed - Potential partnerships or integrations competitors lack **Competitive Positioning Recommendation** - Recommended competitive positioning for $ARGUMENTS - Key differentiators to emphasize - Segments or use cases to target or avoid - Competitive threats to monitor - 12-18 month competitive risks and opportunities ## Best Practices - Research current competitor websites, pricing pages, and customer reviews - Use web search to identify product launches, funding, executive moves - Distinguish between direct competitors and adjacent alternatives - Validate competitive insights across multiple sources - Identify both obvious and subtle differentiation opportunities - Consider customer pain points not yet addressed in market - Look for emerging competitors or new market entrants - Flag competitors gaining traction or gaining market share - Consider long-term competitive dynamics and market shifts --- ### Further Reading - [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques) - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.