From pm-gtm
Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-gtm:competitor-teardownThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
Ask the user for these if not provided:
One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary.
Describe a 2x2 positioning map in text form (since you can't render images):
| Feature / Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
|---|---|---|---|---|
| [Feature] | ✅ / ❌ / 🟡 Partial |
Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk.
Include 10–15 rows. If user hasn't provided feature details, note which cells need to be verified.
For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):
[Competitor Name]
Produce a clean SWOT for the user's product in the context of this competitive landscape:
3–5 actionable recommendations based on the analysis. Frame each as: "Given [observation], [your product] should [action] to [outcome]."
Guides 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.
npx claudepluginhub kriptoburak/mohitagw-pm-claude-skills --plugin pm-gtm