/competitive-analysis
Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities
$ npx -y skills add phuryn/pm-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/competitive-analysis
Context preview
What this command does when you run it.
Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities
Command definition
competitive-analysis.mddescription: Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities
argument-hint: "<your product or market>"
/competitive-analysis -- Competitive Landscape Analysis
Research and analyze your competitive landscape. Identifies direct and indirect competitors, maps positioning, and surfaces differentiation opportunities.
Invocation
/competitive-analysis AI-powered project management tools
/competitive-analysis Our product vs Notion, Asana, and Monday.com
/competitive-analysis [upload a competitor list or market brief]
Workflow
Step 1: Understand the Competitive Context
Ask:
- What is your product? What category does it compete in?
- Any specific competitors you want analyzed? Or should I identify them?
- What's the lens? (feature comparison, positioning, pricing, go-to-market)
- What will you use this analysis for? (strategy, sales enablement, investor pitch, product roadmap)
Step 2: Identify Competitors
Apply the **competitor-analysis** skill:
- Identify 5 direct competitors (same category, same buyer)
- Identify 2-3 indirect competitors (different approach, same job-to-be-done)
- Note emerging/disruptive players if relevant
- Use web research to gather current information
Step 3: Analyze Each Competitor
For each competitor:
- **Positioning**: How they describe themselves, target audience, key messaging
- **Strengths**: What they do well, where they win
- **Weaknesses**: Where they fall short, common complaints
- **Pricing**: Model and price points (if public)
- **Market traction**: Funding, team size, customer base signals
- **Recent moves**: New features, partnerships, pivots
Step 4: Generate Competitive Analysis
## Competitive Analysis: [Your Product/Market]
**Date**: [today]
**Analyzed**: [count] competitors
### Market Overview
[2-3 sentences on market dynamics, trends, and where it's heading]
### Competitive Landscape
| Competitor | Category | Target | Positioning | Strength | Weakness |
|-----------|----------|--------|------------|----------|----------|
### Feature Comparison Matrix
| Capability | Your Product | Competitor A | Competitor B | Competitor C |
|-----------|-------------|-------------|-------------|-------------|
### Positioning Map
[2x2 matrix showing competitive positioning on key dimensions]
### Differentiation Opportunities
1. **[Opportunity]** — [why it's defensible and valuable]
2. ...
### Competitive Threats
1. **[Threat]** — [what to watch for, recommended response]
2. ...
### Recommendations
- **Double down on**: [your unique advantages]
- **Close the gap on**: [table-stakes features you're missing]
- **Ignore**: [competitor moves that aren't worth responding to]
Save as markdown.
Step 5: Offer Next Steps
- "Want me to **create a battlecard** for sales against a specific competitor?"
- "Should I **develop positioning** that differentiates from the top competitors?"
- "Want me to **identify feature gaps** to close and add to the roadmap?"
Notes
- Web research is used for current competitor data — results are as fresh as available sources
- Distinguish between "table stakes" (must-have to compete) and "differentiators" (must-have to win)
- Don't just list features — analyze *why* competitors make the choices they make
- Pricing intelligence should note whether pricing is public, usage-based, or requires sales contact
- Update this analysis quarterly — competitive landscapes shift fast
Read more
description: Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities argument-hint: "<your product or market>"
/competitive-analysis -- Competitive Landscape Analysis
Research and analyze your competitive landscape. Identifies direct and indirect competitors, maps positioning, and surfaces differentiation opportunities.
Invocation
/competitive-analysis AI-powered project management tools /competitive-analysis Our product vs Notion, Asana, and Monday.com /competitive-analysis [upload a competitor list or market brief]
Workflow
Step 1: Understand the Competitive Context
Ask:
- What is your product? What category does it compete in?
- Any specific competitors you want analyzed? Or should I identify them?
- What's the lens? (feature comparison, positioning, pricing, go-to-market)
- What will you use this analysis for? (strategy, sales enablement, investor pitch, product roadmap)
Step 2: Identify Competitors
Apply the **competitor-analysis** skill:
- Identify 5 direct competitors (same category, same buyer)
- Identify 2-3 indirect competitors (different approach, same job-to-be-done)
- Note emerging/disruptive players if relevant
- Use web research to gather current information
Step 3: Analyze Each Competitor
For each competitor:
- **Positioning**: How they describe themselves, target audience, key messaging
- **Strengths**: What they do well, where they win
- **Weaknesses**: Where they fall short, common complaints
- **Pricing**: Model and price points (if public)
- **Market traction**: Funding, team size, customer base signals
- **Recent moves**: New features, partnerships, pivots
Step 4: Generate Competitive Analysis
## Competitive Analysis: [Your Product/Market] **Date**: [today] **Analyzed**: [count] competitors ### Market Overview [2-3 sentences on market dynamics, trends, and where it's heading] ### Competitive Landscape | Competitor | Category | Target | Positioning | Strength | Weakness | |-----------|----------|--------|------------|----------|----------| ### Feature Comparison Matrix | Capability | Your Product | Competitor A | Competitor B | Competitor C | |-----------|-------------|-------------|-------------|-------------| ### Positioning Map [2x2 matrix showing competitive positioning on key dimensions] ### Differentiation Opportunities 1. **[Opportunity]** — [why it's defensible and valuable] 2. ... ### Competitive Threats 1. **[Threat]** — [what to watch for, recommended response] 2. ... ### Recommendations - **Double down on**: [your unique advantages] - **Close the gap on**: [table-stakes features you're missing] - **Ignore**: [competitor moves that aren't worth responding to]
Save as markdown.
Step 5: Offer Next Steps
- "Want me to **create a battlecard** for sales against a specific competitor?"
- "Should I **develop positioning** that differentiates from the top competitors?"
- "Want me to **identify feature gaps** to close and add to the roadmap?"
Notes
- Web research is used for current competitor data — results are as fresh as available sources
- Distinguish between "table stakes" (must-have to compete) and "differentiators" (must-have to win)
- Don't just list features — analyze *why* competitors make the choices they make
- Pricing intelligence should note whether pricing is public, usage-based, or requires sales contact
- Update this analysis quarterly — competitive landscapes shift fast
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
Other commands on pm-skills.
- /derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI
Open command - /document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply
Open command - /performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact
Open command - /security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks
Open command - /ship-check
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage, and compile the results
Open command - /analyze-cohorts
Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends
Open command

