
Discover Competitive Analysis
- 556 installs
- 518 repo stars
- Updated August 4, 2026
- product-on-purpose/pm-skills
discover-competitive-analysis is a Claude Code agent skill that generates a structured competitive analysis document comparing features, positioning, pricing, and strategy across market alternatives for developers and pr
About
discover-competitive-analysis is an Apache-2.0 agent skill from product-on-purpose/pm-skills (version 2.1.0) that walks an AI through a 7-step competitive research workflow and fills an 11-section TEMPLATE.md output. The skill scopes 3-5 competitors, gathers public intelligence from pricing pages and review sites, builds a feature comparison matrix with Full/Partial/None ratings, maps a 2x2 positioning chart, and documents strengths, gaps, and strategic recommendations with source confidence levels. Developers reach for discover-competitive-analysis when entering a new market, planning SaaS differentiation, preparing quarterly strategy reviews, or onboarding engineers to competitive context before PRD or architecture work. Invoke it via /pm-skills:discover-competitive-analysis on Claude Code or $discover-competitive-analysis on Codex.
- discover-competitive-analysis
- AI & Agent Building
- AI-coding skill
Discover Competitive Analysis by the numbers
- 556 all-time installs (skills.sh)
- +33 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,656 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/product-on-purpose/pm-skills --skill discover-competitive-analysisAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 556 |
|---|---|
| repo stars | ★ 518 |
| Last updated | August 4, 2026 |
| Repository | product-on-purpose/pm-skills ↗ |
How do you structure a SaaS competitive analysis?
Helps with ai & agent building tasks.
Who is it for?
Developers and tech leads who need a repeatable competitive intelligence artifact before roadmap, PRD, or build-vs-buy decisions.
Skip if: Teams needing TAM or market sizing totals rather than competitor positioning should use discover-market-sizing instead of this skill.
When should I use this skill?
A developer asks to map competitors, compare SaaS features and pricing, or draft differentiation strategy before entering a market.
What you get
Markdown competitive analysis with feature matrix, pricing comparison, 2x2 positioning map, competitor deep dives, gap analysis, and sourced recommendations
- Competitive analysis markdown report
- Feature comparison matrix with capability ratings
- 2x2 positioning map with strategic recommendations
By the numbers
- Version 2.1.0 with an 11-section TEMPLATE.md output structure
- 7-step research workflow with a 6-item quality checklist
- Scopes 3-5 competitors across direct, indirect, and disruptor categories
Files
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Competitive Analysis
A competitive analysis provides structured insight into the competitive landscape, helping product teams understand where they stand relative to alternatives and identify opportunities for differentiation. Rather than exhaustively cataloging every competitor, an effective analysis focuses on actionable insights that inform product strategy.
When to Use
- Before entering a new market or launching a new product
- When planning differentiation strategy for an existing product
- During quarterly or annual strategic planning reviews
- When evaluating build vs. buy decisions
- After losing deals to understand competitive positioning
- When onboarding new product team members to the market context
When NOT to Use
- You need market size rather than competitor positioning -> use
discover-market-sizing - You are stress-testing strategic differentiation across the whole business model -> use
foundation-lean-canvas, ortool-foundation-sprint-differentiationinside a Foundation Sprint - You want to understand why customers switch products -> use
define-jtbd-canvas; it examines competing solutions through the job lens - The landscape is already mapped and you need the problem framed -> use
define-problem-statement
Instructions
When asked to create a competitive analysis, follow these steps:
1. Define the Scope Clarify what you're analyzing: a specific feature area, overall product positioning, or pricing strategy. Identify 3-5 key competitors.direct competitors (same solution), indirect competitors (different solution to same problem), and potential disruptors.
2. Gather Intelligence Research each competitor through public sources: websites, pricing pages, G2/Capterra reviews, press releases, job postings, and customer testimonials. Note what you can verify vs. what you're inferring.
3. Build the Feature Matrix Create a comparison grid of key capabilities. Focus on features that matter to your target customers, not exhaustive checklists. Use consistent ratings (e.g., Full, Partial, None, Unknown).
4. Analyze Positioning Map competitors on a 2x2 positioning matrix using dimensions relevant to your market (e.g., price vs. features, ease of use vs. power, SMB vs. enterprise). Identify white space opportunities.
5. Assess Strengths and Weaknesses For each competitor, document genuine strengths (what they do better than you) and weaknesses (where they fall short). Avoid dismissing competitors.respect drives better strategy.
6. Identify Strategic Implications Translate observations into actionable recommendations: where to compete head-on, where to differentiate, what messaging to emphasize, and what gaps represent opportunities.
7. Note Confidence Levels Mark which conclusions are based on verified data vs. inference. Competitive intelligence has varying reliability.be honest about uncertainty.
Output Format
Use the template in references/TEMPLATE.md to structure the output. A complete analysis fills every template section: Overview; Market Context; Competitors Analyzed; Feature Comparison Matrix; Pricing Comparison; Positioning Map; Competitor Deep Dives; Competitive Gaps and Opportunities; Strategic Recommendations; Sources and Confidence; and Next Steps.
Quality Checklist
Before finalizing, verify:
- [ ] Scope is clearly defined (what market, segment, use case)
- [ ] 3-5 competitors are analyzed, including direct and indirect
- [ ] Feature comparison focuses on customer-relevant capabilities
- [ ] Positioning map uses meaningful, differentiated dimensions
- [ ] Strengths acknowledge where competitors genuinely excel
- [ ] Recommendations are specific and actionable
- [ ] Sources and confidence levels are documented
Examples
See references/EXAMPLE.md for a completed example.
Scenario: AI meeting-notes competitive landscape
This is the INPUT brief for an output-quality eval. The skill arm and the control arm each receive everything below (and nothing else about how to do the work) and produce a competitive-analysis artifact for it. Judges never see this header.
Context
Our product: "Recall" (working name), a new AI meeting-notes assistant that joins video calls, transcribes them, and produces summaries and action items. We are pre-launch, targeting small revenue-team users (sales and customer success at companies of 20-200 people).
Why now: we are deciding how to position and where to differentiate before a public launch next quarter. We have build capacity for one or two genuinely distinctive bets, not parity across the board.
What we know about the landscape (raw, mixed-reliability notes)
- Otter.ai - broad, well-known, freemium. Strong transcription, large free tier. Heard from two
prospects it is "generic" and "not built for sales." Pricing roughly $8-20/user/mo (from their site).
- Fireflies.ai - integrations-heavy (CRM, Slack), bot joins calls. Positions on "search across all
your meetings." Mid-market traction. Pricing similar band.
- Gong - enterprise revenue-intelligence platform, not just notes; deal analytics, coaching.
Expensive, long sales cycle, aimed at larger orgs. Strong brand with VP Sales buyers.
- Granola - newer, "AI notepad" that does not send a bot into the call; runs locally-ish, design-
led, popular with founders. Less CRM depth. Unclear team-admin story.
- Zoom AI Companion - bundled free with Zoom. "Good enough" summaries for many. The default many
teams already have.
Things we are unsure about: exact current pricing for Gong and Granola, how good each one's CRM sync actually is in practice, and how each handles non-Zoom platforms (Meet, Teams).
Our hunch at differentiation: deep, trustworthy CRM write-back (auto-update the opportunity) and sales-specific summaries (next steps, risks, competitor mentions). Unvalidated.
Audience for the artifact: the founding team and the first PM, to decide positioning and the one or two differentiation bets.
{
"schema": 1,
"skill": "discover-competitive-analysis",
"runs_per_query": 3,
"trigger_threshold": 0.5,
"queries": [
{
"q": "Do a competitive analysis of the top five project-management tools before we enter that market",
"expect": "trigger",
"split": "train"
},
{
"q": "We keep losing enterprise deals to two rivals; break down their features, pricing, and positioning against ours",
"expect": "trigger",
"split": "train",
"notes": "Intent-only ask; losing deals is a listed use case"
},
{
"q": "Map the competitive landscape for AI meeting assistants: direct, indirect, and potential disruptors",
"expect": "trigger",
"split": "train"
},
{
"q": "Leadership wants to know where we can differentiate; compare our product against the main alternatives on features and strategy",
"expect": "trigger",
"split": "train"
},
{
"q": "We're weighing build versus buy for analytics; analyze the vendor landscape so we understand the alternatives",
"expect": "trigger",
"split": "train"
},
{
"q": "Put together the market-landscape section for our annual planning review, comparing positioning across our top competitors",
"expect": "trigger",
"split": "train"
},
{
"q": "Create a competitive analysis of Figma, Sketch, and Penpot for our design-tool strategy",
"expect": "trigger",
"split": "validation"
},
{
"q": "A well-funded startup just entered our space; assess how their offering stacks up and where we're exposed",
"expect": "trigger",
"split": "validation",
"notes": "Intent-only ask, no artifact keyword"
},
{
"q": "Onboard our new PM with a structured overview of who we compete with and how we win",
"expect": "trigger",
"split": "validation"
},
{
"q": "What are the feature gaps between us and the category leader, and where should we differentiate?",
"expect": "trigger",
"split": "validation"
},
{
"q": "How big is the addressable market for B2B expense tools? Give me TAM, SAM, and SOM",
"expect": "no-trigger",
"split": "train",
"near_miss_of": "discover-market-sizing",
"notes": "Market size rather than competitor positioning, per When NOT to Use"
},
{
"q": "I want to understand why customers switch from competitors to us, in terms of the progress they're trying to make",
"expect": "no-trigger",
"split": "validation",
"near_miss_of": "define-jtbd-canvas",
"notes": "Switching examined through the job lens, per When NOT to Use"
},
{
"q": "Stress-test our differentiation across the whole business model on a lean canvas",
"expect": "no-trigger",
"split": "train",
"notes": "Whole-business-model differentiation; foundation-lean-canvas territory"
},
{
"q": "The landscape is already mapped; now frame the problem we're going after as a problem statement",
"expect": "no-trigger",
"split": "train"
},
{
"q": "Synthesize the win-loss interview notes from the deals we lost last quarter",
"expect": "no-trigger",
"split": "validation"
},
{
"q": "Draft the PRD for the comparison-table feature on our pricing page",
"expect": "no-trigger",
"split": "train",
"notes": "Contains comparison language but is a specification ask"
},
{
"q": "Debug why this Express endpoint returns a 500 only in production",
"expect": "no-trigger",
"split": "train",
"notes": "Unrelated debugging ask"
},
{
"q": "Write a SQL query joining accounts and subscriptions to find expansion revenue",
"expect": "no-trigger",
"split": "validation",
"notes": "Unrelated technical ask"
},
{
"q": "Book a rental car and hotel for my trip to the trade show in Las Vegas",
"expect": "no-trigger",
"split": "train",
"notes": "Unrelated logistics ask"
},
{
"q": "Build a persona for the economic buyer in our mid-market accounts",
"expect": "no-trigger",
"split": "validation"
}
]
}
discover-competitive-analysis - Version History
| Version | Date | Release | Effort | Type | Summary |
|---|---|---|---|---|---|
| 2.1.0 | 2026-06-10 | v2.26.0 | F-12-batch-3 | minor | Quality convergence: When NOT to Use + output-contract enumeration (F-12 Batch 3) |
| 2.0.0 | 2026-01-26 | - | - | baseline | Prior published version |
2.1.0 (2026-06-10)
Quality-convergence minor (F-12 Batch 3): added a "When NOT to Use" section with boundary pointers to neighboring skills, and the Output Format now enumerates the template sections a complete artifact fills. No template or example changes.
2.0.0 (2026-01-26)
Baseline row for the prior published version; see git history for its changes.
Competitive Analysis: Project Management Software for SMB Teams
Overview
Analysis Scope: Core project management features for teams of 10-50 people Target Segment: Small and medium businesses with data-driven culture Date: January 2026 Analyst: Product Strategy Team
Market Context
The project management software market continues to grow as remote and hybrid work becomes standard. While established players dominate, there's increasing demand for better reporting and analytics capabilities.
Market Size: $6.7B (2025), projected $9.8B by 2028 Growth Trend: Growing at 12% CAGR Key Trends:
- AI-assisted task management and prioritization
- Integration with communication tools (Slack, Teams)
- Demand for real-time dashboards and custom reporting
- Shift from per-seat to usage-based pricing models
Competitors Analyzed
| Competitor | Type | Target Market | Founded | Funding/Size |
|---|---|---|---|---|
| Asana | Direct | Mid-market teams | 2008 | Public (NYSE: ASAN) |
| Monday.com | Direct | SMB to Enterprise | 2012 | Public (NASDAQ: MNDY) |
| ClickUp | Direct | SMB, price-sensitive | 2017 | $537M raised |
| Notion | Indirect | Startups, knowledge workers | 2016 | $10B valuation |
Feature Comparison Matrix
| Feature | TaskFlow (Ours) | Asana | Monday.com | ClickUp | Notion |
|---|---|---|---|---|---|
| Task Management | Full | Full | Full | Full | Full |
| Kanban Boards | Full | Full | Full | Full | Full |
| Gantt Charts | Full | Full | Full | Full | Partial |
| Time Tracking | Full | Partial | Full | Full | None |
| Custom Fields | Full | Full | Full | Full | Full |
| Reporting Dashboard | Full | Partial | Full | Full | None |
| Custom Reports | Full | Partial | Partial | Partial | None |
| Resource Planning | Full | Partial | Full | Partial | None |
| AI Prioritization | Full | Partial | Partial | Partial | Partial |
| API Access | Full | Full | Full | Full | Full |
Pricing Comparison
| Competitor | Entry Price | Mid-Tier | Enterprise | Pricing Model |
|---|---|---|---|---|
| TaskFlow (Ours) | $8/user/mo | $15/user/mo | Custom | Per seat |
| Asana | Free (basic) | $11/user/mo | $25/user/mo | Per seat |
| Monday.com | $9/seat/mo | $12/seat/mo | $19/seat/mo | Per seat (min 3) |
| ClickUp | Free (limited) | $7/user/mo | $12/user/mo | Per seat |
| Notion | Free (personal) | $10/user/mo | $15/user/mo | Per seat |
Positioning Map
Axis X: Price (Low to High) Axis Y: Analytics Depth (Basic to Advanced)
[Advanced Analytics]
|
| [TaskFlow - Us]
|
[Monday.com] |
|
[Low Price] ---------------+--------------- [High Price]
|
[ClickUp] | [Asana]
|
[Notion] |
|
[Basic Analytics]White Space Identified: Advanced analytics at mid-market price point. Current solutions either offer basic reporting (ClickUp, Notion) or charge enterprise prices for advanced analytics (Asana Portfolio).
Competitor Deep Dives
Asana
Overview: Enterprise-grade work management platform with strong workflow automation and portfolio management features. Target Customer: Mid-market to enterprise teams with complex workflows Key Differentiator: Workflow Builder and portfolio-level visibility
Strengths:
- Excellent workflow automation capabilities
- Strong enterprise security and compliance certifications
- Deep integrations with 200+ business tools
- Mature mobile applications
Weaknesses:
- Premium features require expensive tiers
- Reporting limited without Business/Enterprise plans
- Can feel complex for small teams
- Time tracking requires third-party integration
Recent Moves: Launched AI "Work Graph" features in Q4 2025; acquired small analytics startup in 2025.
---
Monday.com
Overview: Highly visual, flexible work OS with strong customization and automation capabilities. Target Customer: Visual thinkers in SMB to mid-market companies Key Differentiator: Extreme flexibility and colorful, intuitive interface
Strengths:
- Highly customizable workflows and views
- Excellent visual appeal and user experience
- Strong automation without coding
- Growing CRM and dev management add-ons
Weaknesses:
- Minimum 3-seat purchase on paid plans
- Can become expensive as features scale
- Reporting depth limited compared to dedicated BI tools
- Performance can lag with large datasets
Recent Moves: Expanded into CRM and developer workflows; launched Monday AI assistant for task creation.
---
ClickUp
Overview: Feature-rich, all-in-one productivity platform competing aggressively on price and feature breadth. Target Customer: Price-conscious teams wanting maximum features Key Differentiator: Everything included at lower price points
Strengths:
- Exceptional value for features offered
- Generous free tier for small teams
- Rapid feature development pace
- Docs, whiteboards, and time tracking included
Weaknesses:
- Interface can feel cluttered and overwhelming
- Feature depth sometimes sacrificed for breadth
- Reporting and analytics relatively basic
- Occasional performance and reliability issues
Recent Moves: Major UI refresh in late 2025; expanding AI capabilities across platform.
---
Notion
Overview: Flexible workspace combining notes, docs, databases, and basic project management. Target Customer: Startups and knowledge workers valuing flexibility Key Differentiator: Unparalleled flexibility as connected workspace
Strengths:
- Infinitely flexible building blocks
- Excellent for documentation and wikis
- Strong template ecosystem and community
- Clean, distraction-free interface
Weaknesses:
- Not purpose-built for project management
- No native Gantt charts or resource planning
- Limited reporting and analytics capabilities
- Performance degrades with large databases
Recent Moves: Launched Notion Projects for structured PM workflows; acquired calendar startup.
Competitive Gaps and Opportunities
| Gap | Opportunity | Strategic Value | Difficulty |
|---|---|---|---|
| Advanced analytics at mid-market pricing | Position as "BI-powered PM tool" | High | Medium |
| Native resource utilization tracking | Appeal to services firms and agencies | High | Medium |
| Customizable executive dashboards | Differentiate on strategic visibility | High | Low |
| AI-powered project health scoring | Early mover advantage in emerging space | Medium | High |
Strategic Recommendations
Where to Compete Head-On
1. Core PM features: Must match table-stakes functionality (tasks, boards, basic views) to avoid disqualification 2. Integrations: Prioritize Slack, Teams, and Google Workspace integrations to match competitor ecosystem plays
Where to Differentiate
1. Analytics depth: Make reporting and dashboards a primary differentiator, not an afterthought. Position as "the PM tool for data-driven teams" 2. Resource intelligence: Build predictive resource planning that shows utilization forecasts.no competitor does this well at our price point 3. Time-to-insight: Focus on immediate visibility vs. "set up dashboards later" approach of competitors
Messaging Implications
- Lead with analytics and visibility in all positioning.this is our white space
- Avoid feature-count battles with ClickUp; emphasize depth over breadth
- Target messaging at team leads and operations managers who care about metrics
- Use "finally, a PM tool that shows you what's really happening" as positioning theme
Watch List
- Asana's AI roadmap.they have resources to move quickly
- ClickUp reliability improvements.if they solve stability, they're formidable
- Monday.com analytics investments.likely to improve given market demand
- New entrants from BI space moving into PM (e.g., if Tableau/Looker launched PM features)
Sources and Confidence
| Information Type | Source | Confidence |
|---|---|---|
| Feature data | Product websites, free trials | High |
| Pricing | Public pricing pages | High |
| Market size | Gartner, IDC reports 2025 | Medium |
| Strategy inference | Press releases, job postings | Medium |
| Customer sentiment | G2, Capterra reviews | Medium |
Next Steps
- [ ] Validate analytics positioning with customer interviews (5 prospects)
- [ ] Create competitive battle cards for sales team
- [ ] Develop demo script emphasizing analytics differentiation
- [ ] Set up competitor monitoring for product launches
- [ ] Schedule quarterly refresh of this analysis
---
Analysis valid as of January 2026. Competitive landscape changes frequently; recommend quarterly updates.
Competitive Analysis: [Market/Product Area]
Overview
Analysis Scope: [What specific area is being analyzed] Target Segment: [Customer segment this analysis focuses on] Date: [When analysis was conducted] Analyst: [Who prepared this]
Market Context
<!-- Brief overview of the market being analyzed -->
Market Size: [TAM/SAM/SOM if available] Growth Trend: [Growing, stable, declining] Key Trends:
- [Trend 1]
- [Trend 2]
- [Trend 3]
Competitors Analyzed
| Competitor | Type | Target Market | Founded | Funding/Size |
|---|---|---|---|---|
| [Name] | Direct/Indirect | [Segment] | [Year] | [Info] |
| [Name] | Direct/Indirect | [Segment] | [Year] | [Info] |
| [Name] | Direct/Indirect | [Segment] | [Year] | [Info] |
| [Name] | Direct/Indirect | [Segment] | [Year] | [Info] |
Feature Comparison Matrix
<!-- Rate as: Full, Partial, None, Unknown -->
| Feature | Our Product | Competitor A | Competitor B | Competitor C | Competitor D |
|---|---|---|---|---|---|
| [Feature 1] | |||||
| [Feature 2] | |||||
| [Feature 3] | |||||
| [Feature 4] | |||||
| [Feature 5] | |||||
| [Feature 6] | |||||
| [Feature 7] | |||||
| [Feature 8] |
Pricing Comparison
| Competitor | Entry Price | Mid-Tier | Enterprise | Pricing Model |
|---|---|---|---|---|
| [Name] | [Price] | [Price] | [Price] | [Per seat/usage/flat] |
| [Name] | [Price] | [Price] | [Price] | [Per seat/usage/flat] |
| [Name] | [Price] | [Price] | [Price] | [Per seat/usage/flat] |
| [Name] | [Price] | [Price] | [Price] | [Per seat/usage/flat] |
Positioning Map
<!-- Describe the 2x2 positioning map -->
Axis X: [Dimension 1 - e.g., Price (Low to High)] Axis Y: [Dimension 2 - e.g., Functionality (Basic to Advanced)]
[High Y]
|
| [Competitor C]
[Competitor A] |
|
[Low X] ---------------+--------------- [High X]
|
[Our Product] | [Competitor B]
|
| [Competitor D]
[Low Y]White Space Identified: [Underserved positioning opportunities]
Competitor Deep Dives
[Competitor A Name]
Overview: [1-2 sentence description] Target Customer: [Who they serve best] Key Differentiator: [Their main selling point]
Strengths:
- [Genuine strength 1]
- [Genuine strength 2]
- [Genuine strength 3]
Weaknesses:
- [Weakness 1]
- [Weakness 2]
- [Weakness 3]
Recent Moves: [Notable product launches, funding, acquisitions]
---
[Competitor B Name]
Overview: [1-2 sentence description] Target Customer: [Who they serve best] Key Differentiator: [Their main selling point]
Strengths:
- [Genuine strength 1]
- [Genuine strength 2]
- [Genuine strength 3]
Weaknesses:
- [Weakness 1]
- [Weakness 2]
- [Weakness 3]
Recent Moves: [Notable product launches, funding, acquisitions]
---
[Competitor C Name]
Overview: [1-2 sentence description] Target Customer: [Who they serve best] Key Differentiator: [Their main selling point]
Strengths:
- [Genuine strength 1]
- [Genuine strength 2]
- [Genuine strength 3]
Weaknesses:
- [Weakness 1]
- [Weakness 2]
- [Weakness 3]
Recent Moves: [Notable product launches, funding, acquisitions]
---
[Competitor D Name]
Overview: [1-2 sentence description] Target Customer: [Who they serve best] Key Differentiator: [Their main selling point]
Strengths:
- [Genuine strength 1]
- [Genuine strength 2]
- [Genuine strength 3]
Weaknesses:
- [Weakness 1]
- [Weakness 2]
- [Weakness 3]
Recent Moves: [Notable product launches, funding, acquisitions]
Competitive Gaps and Opportunities
<!-- Where the market is underserved -->
| Gap | Opportunity | Strategic Value | Difficulty |
|---|---|---|---|
| [Gap 1] | [Opportunity] | High/Medium/Low | High/Medium/Low |
| [Gap 2] | [Opportunity] | High/Medium/Low | High/Medium/Low |
| [Gap 3] | [Opportunity] | High/Medium/Low | High/Medium/Low |
Strategic Recommendations
Where to Compete Head-On
<!-- Features or areas where we should match or beat competitors --> 1. [Recommendation] 2. [Recommendation]
Where to Differentiate
<!-- Areas where we should take a different approach --> 1. [Recommendation] 2. [Recommendation]
Messaging Implications
<!-- How competitive insights should inform positioning -->
- [Messaging guidance 1]
- [Messaging guidance 2]
Watch List
<!-- Competitive developments to monitor -->
- [Item to watch]
- [Item to watch]
Sources and Confidence
| Information Type | Source | Confidence |
|---|---|---|
| Feature data | [Source] | High/Medium/Low |
| Pricing | [Source] | High/Medium/Low |
| Market size | [Source] | High/Medium/Low |
| Strategy inference | [Source] | High/Medium/Low |
Next Steps
- [ ] [Action item 1]
- [ ] [Action item 2]
- [ ] [Action item 3]
---
Analysis valid as of [date]. Competitive landscape changes frequently; recommend quarterly updates.
Related skills
How it compares
Pick discover-competitive-analysis when you need competitor feature and positioning maps; use discover-market-sizing for TAM estimates or define-problem-statement once the landscape is already mapped.
FAQ
What does discover-competitive-analysis output?
discover-competitive-analysis outputs a markdown competitive analysis following references/TEMPLATE.md with 11 sections: overview, market context, competitors analyzed, feature matrix, pricing comparison, positioning map, deep dives, gaps, recommendations, sources with confidence
How many competitors should discover-competitive-analysis cover?
discover-competitive-analysis scopes 3-5 key competitors including direct alternatives, indirect substitutes, and potential disruptors. The quality checklist requires both direct and indirect coverage with customer-relevant feature ratings.
How do you invoke discover-competitive-analysis in Claude Code?
discover-competitive-analysis runs via /pm-skills:discover-competitive-analysis with market context on Claude Code, or $discover-competitive-analysis on Codex. The skill file lives at skills/discover-competitive-analysis/SKILL.md in the pm-skills repository.