From pm-essentials
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-essentials:competitive-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create structured competitive analyses for product decision-making.
Create structured competitive analyses for product decision-making.
Ask the user for these if not provided:
For each competitor:
| Feature | Us | Competitor A | Competitor B | Competitor C |
|---|---|---|---|---|
| [Feature] | ✅ Full | ⚠️ Limited | ❌ None | ✅ Full |
Legend: ✅ Full (production-ready) · ⚠️ Limited/Beta · ❌ None
Include notes on quality and implementation differences where significant.
| Plan | Us | Competitor A | Competitor B |
|---|---|---|---|
| Free/Trial | [price] | [price] | [price] |
| Pro | [price] | [price] | [price] |
| Enterprise | [price] | [price] | [price] |
Position competitors on two key dimensions relevant to the market:
Whitespace Opportunities: [Underserved segments]
Why We Win:
Why We Lose:
Immediate Actions (0-3 months):
Medium-term (3-12 months):
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-essentialsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 8, 2026