competitor-teardown
Competitor Teardown Skill
This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
Required Inputs
Ask the user for these if not provided:
- Your product (name + one-line description)
- Competitors to analyse (list 2–5 names; if not provided, ask)
- Analysis depth (quick overview / detailed teardown)
- Primary use case for this analysis (e.g. sales enablement, investor deck, internal strategy, product planning)
Output Structure
1. Competitive Landscape Overview
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.
2. Positioning Map
Describe a 2x2 positioning map in text form (since you can't render images):
- Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness")
- Place each competitor in one quadrant with a one-sentence rationale
- Place the user's product and highlight the strategic implication
3. Feature Comparison Table
| 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.
4. Messaging Analysis
For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):
[Competitor Name]
- Their primary claim: [what they say they do]
- Target audience signal: [who they seem to be targeting based on language/imagery]
- Emotional hook: [fear / aspiration / authority / speed / simplicity]
- Gap or weakness in their messaging: [what they don't address that your product could own]
5. SWOT Summary
Produce a clean SWOT for the user's product in the context of this competitive landscape:
- Strengths: [2–3 genuine differentiators]
- Weaknesses: [2–3 honest gaps or vulnerabilities]
- Opportunities: [2–3 market gaps or competitor weaknesses to exploit]
- Threats: [2–3 competitor moves or market shifts to watch]
6. Strategic Recommendations
3–5 actionable recommendations based on the analysis. Frame each as: "Given [observation], [your product] should [action] to [outcome]."
Quality Checks
- Axes on positioning map are meaningful and specific to this market
- Feature table includes strategic notes on key differentiators
- Messaging analysis covers all named competitors
- SWOT is honest — Weaknesses and Threats should not be softened
- Recommendations are specific and actionable, not generic strategy advice
Example Trigger Phrases
- "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
- "Tear down [Competitor]'s positioning"
- "Give me a competitive landscape for [market]"
- "Build a SWOT for our product against [competitor]"
More from mohitagw15856/pm-claude-skills
user-research-synthesis
Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps.
26prd-template
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
20stakeholder-update
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
19competitive-analysis
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.
18meeting-notes
Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.
17executive-summary
Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.
15