[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YYMY41JHFVVC9B0W2H7W2":3,"skill-same:01M72YYMY41JHFVVC9B0W2H7W2":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72YYMY41JHFVVC9B0W2H7W2","competitive-analysis-templates",null,"Master competitive analysis templates including competitor deep-dives, battle cards, feature comparison matrices, and win\u002Floss analysis. Use when analyzing competitors, creating battle cards for sales, positioning against alternatives, tracking competitive moves, or preparing for competitive threats. Covers competitive intelligence frameworks, positioning strategies, and templates from Crayon, Klue, and April Dunford.","enigmaicon-eng\u002FAI-Enterprise-OS","enigmaicon-eng","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269773191?v=4","01M72YXXYN7Q7BYRHV8RAVYNWD","01M72YXXZPW35H56D6F1XSK84D",2,"MIT","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: competitive-analysis-templates\ndescription: Master competitive analysis templates including competitor deep-dives, battle cards, feature comparison matrices, and win\u002Floss analysis. Use when analyzing competitors, creating battle cards for sales, positioning against alternatives, tracking competitive moves, or preparing for competitive threats. Covers competitive intelligence frameworks, positioning strategies, and templates from Crayon, Klue, and April Dunford.\n---\n\n# Competitive Analysis Templates\n\nTemplates for analyzing competitors, enabling sales teams, and defining strategic market positioning.\n\n## When to Use This Skill\n\n**Auto-loaded by agents**:\n\n- `market-analyst` - For competitor deep-dives, battle cards, and positioning maps\n\n**Use when you need**:\n\n- Analyzing competitor strategies and offerings\n- Creating sales battle cards\n- Building feature comparison matrices\n- Tracking competitive intelligence\n- Conducting win\u002Floss analysis\n- Defining differentiation strategy\n- Monitoring competitive threats\n- Positioning against alternatives\n\n## What is Competitive Analysis?\n\nCompetitive analysis helps you:\n\n- **Understand** your market position and competitive landscape\n- **Identify** differentiation opportunities and white space\n- **Enable** sales teams to win competitive deals\n- **Inform** product roadmap and strategic decisions\n- **Monitor** competitive threats and market shifts\n\n**NOT**: Copying competitors or building feature parity\n**BUT**: Finding defensible differentiation and strategic positioning\n\n**Good competitive analysis**: Actionable, evidence-based, honest about trade-offs, regularly updated\n\n**Bad competitive analysis**: Feature lists without context, outdated, biased, not used by teams\n\n---\n\n## Evidence Standards\n\n**Core principle:** All competitive intelligence must be based on verifiable public sources. Strategic analysis and recommendations are core value, but factual claims require source attribution.\n\n**Research requirements:**\n\n1. **Use verifiable public sources**\n   - Competitor websites, product pages, and documentation\n   - Pricing pages (with URLs and date accessed)\n   - Review sites (G2, Capterra, TrustRadius) with specific review citations\n   - News articles, press releases, and public announcements\n   - Product demos, trials, and publicly available materials\n\n2. **Source attribution**\n   - Every claim about competitor features, pricing, or strategy must cite source\n   - Format: \"[Feature\u002FClaim] (Source: [URL], accessed [Date])\"\n   - Review quotes must cite specific review with link\n   - When multiple sources confirm: cite 2-3 representative sources\n\n3. **When data is unavailable**\n   - Explicitly note: \"[Pricing not publicly available]\", \"[Requires product trial]\"\n   - Never fabricate competitor information to complete analysis\n   - Recommend steps to gather missing data (demo request, trial signup)\n   - Note limitation in battle card or analysis\n\n4. **What you CANNOT do**\n   - Fabricate competitor features, pricing, or capabilities\n   - Invent user testimonials or review quotes\n   - Make up market share numbers or competitive statistics\n   - Create fictional customer case studies\n\n5. **What you SHOULD do (core value)**\n   - Provide strategic analysis of competitive landscape\n   - Identify differentiation opportunities based on research\n   - Recommend positioning strategy against competitors\n   - Guide battle card creation and sales enablement\n   - Teach competitive intelligence methodologies\n   - Help interpret competitive data for strategic decisions\n\n**When in doubt:** If public information is unavailable, note the limitation explicitly rather than inventing data. Your strategic expertise in competitive analysis and positioning is your primary value.\n\n---\n\n## Three Core Templates\n\n### 1. Competitor Deep-Dive Analysis\n\n**Purpose**: Comprehensive competitive intelligence for strategic decisions\n\n**Use when**:\n\n- Quarterly competitive reviews\n- Market entry planning\n- Product roadmap planning\n- Understanding new competitive threat\n- Executive briefings\n\n**Key sections**:\n\n- Company overview (size, funding, strategy)\n- Product analysis (features, UX, pricing)\n- Go-to-market strategy (sales, marketing)\n- SWOT analysis (strengths, weaknesses, opportunities, threats)\n- Customer intelligence (reviews, win\u002Floss)\n- Competitive response strategy\n\n**Template**: `assets\u002Fcompetitor-deep-dive-template.md`\n\nComplete template with all sections, example content, intelligence sources\n\n**Time investment**: 8-12 hours initial, 2-3 hours quarterly updates\n\n**Comprehensive guide**: `references\u002Fcompetitive-intel-guide.md`\n\nIntelligence gathering, research techniques, analysis frameworks, organizing intelligence\n\n---\n\n### 2. Battle Card (Sales Enablement)\n\n**Purpose**: Quick-reference competitive enablement for sales teams\n\n**Use when**:\n\n- Sales team faces competitor regularly\n- New competitive threat emerges\n- Need to improve win rates vs. specific competitor\n- Onboarding new sales reps\n\n**Key sections**:\n\n- Quick stats (foundational context)\n- When you'll face them (common scenarios)\n- Where we win (strengths with proof)\n- Where they win (their strengths + how to counter)\n- Common objections & responses\n- Discovery questions (uncover our advantages)\n- Proof points (customer stories, data)\n\n**Template**: `assets\u002Fbattle-card-template.md`\n\nSales-ready format, specific talk tracks, objection handling, proof points\n\n**Format**: 1-2 pages maximum (quick reference for calls)\n\n**Update frequency**: Immediately on competitor changes, monthly review\n\n**Comprehensive guide**: `references\u002Fbattle-card-guide.md`\n\nCreating effective battle cards, sales enablement, training, maintenance, metrics\n\n---\n\n### 3. Positioning & Perceptual Mapping\n\n**Purpose**: Strategic market positioning and visual competitive landscape\n\n**Use when**:\n\n- Strategic planning (annual\u002Fquarterly)\n- Defining product strategy\n- Finding market white space\n- Developing messaging\n- Repositioning product\n\n**Key sections**:\n\n- Perceptual maps (visual market positioning)\n- Positioning statement (April Dunford framework)\n- Differentiation matrix\n- Value proposition map (jobs, pains, gains)\n- Strategic positioning grid\n- Brand positioning\n- Messaging framework\n\n**Template**: `assets\u002Fpositioning-map-template.md`\n\nPerceptual mapping formats, positioning frameworks, differentiation analysis\n\n**Use cases**: Strategic planning, market entry, messaging development\n\n**Comprehensive guide**: `references\u002Fpositioning-guide.md`\n\nPositioning frameworks, differentiation strategies, perceptual mapping, repositioning\n\n---\n\n## Choosing the Right Template\n\n**For strategic planning** → Use all three:\n\n1. Deep-dive analysis (understand landscape)\n2. Positioning map (define your position)\n3. Battle cards (enable execution)\n\n**For sales enablement** → Battle cards:\n\n- Quick reference during calls\n- Specific talk tracks and counters\n- Updated frequently\n\n**For product strategy** → Deep-dive + Positioning:\n\n- Feature gap analysis\n- Market white space\n- Differentiation strategy\n\n**For one competitor** → Start with deep-dive, then battle card\n\n**For market overview** → Positioning map first (landscape), then selective deep-dives\n\n---\n\n## Competitive Intelligence Process\n\n### 1. Gather Intelligence\n\n**Primary sources**:\n\n- Competitor website, demos, trials\n- Customer reviews (G2, Capterra, TrustRadius)\n- Win\u002Floss interviews\n- Customer feedback\n\n**Secondary sources**:\n\n- Press releases, news\n- Job postings (strategic direction)\n- Social media, podcasts\n- Analyst reports\n\n**Source citation requirements:**\n\n- Document URL and access date for every source\n- Cite specific G2\u002FCapterra reviews with links for user quotes\n- Note when information is unavailable: \"[Pricing not public]\"\n- Never fabricate data to fill intelligence gaps\n- Recommend additional research steps for missing data\n\n**Detailed guide**: `references\u002Fcompetitive-intel-guide.md`\n\nResearch techniques, intelligence sources, ethical guidelines, source citation best practices\n\n---\n\n### 2. Analyze Patterns\n\n**Look for**:\n\n- Feature launch velocity (product strategy)\n- Market expansion signals\n- Pricing changes\n- Partnership announcements\n- Messaging shifts\n\n**Framework**: Use SWOT analysis\n\n- **Strengths**: What they do well (facts, evidence)\n- **Weaknesses**: Exploitable gaps (customer complaints, missing features)\n- **Opportunities** (for them): Anticipate their moves\n- **Threats** (to us): How they could hurt us\n\n---\n\n### 3. Act on Insights\n\n**Product decisions**:\n\n- Close critical gaps (table stakes)\n- Exploit weaknesses (differentiation)\n- Defend strengths (maintain advantage)\n\n**Positioning**:\n\n- Find defensible differentiation\n- Avoid head-to-head on their strengths\n- Position in category where you win\n\n**Sales enablement**:\n\n- Create battle cards (competitive situations)\n- Train on objection handling\n- Share win stories\n\n---\n\n## Positioning Frameworks\n\n### April Dunford's 5 Components\n\nWork through in this order:\n\n**1. Competitive Alternatives**: What would customers use if you didn't exist?\n\n**2. Unique Attributes**: What can you do that alternatives can't?\n\n**3. Value (Benefits)**: What do those unique attributes enable?\n\n**4. Target Customer**: Who cares most about that value?\n\n**5. Market Category**: What context makes your value obvious?\n\n**Example**:\n\n> For Series A B2B SaaS companies who need to scale pipeline without growing SDR headcount, [Product] is an AI-powered sales development platform that books 10x more qualified meetings. Unlike Salesforce which requires large SDR teams, we use AI to automate the entire top-of-funnel.\n\n**Complete framework**: `references\u002Fpositioning-guide.md`\n\nPositioning strategies, differentiation, perceptual mapping, validation\n\n---\n\n### Perceptual Mapping\n\n**Purpose**: Visualize competitive landscape, find white space\n\n**Common axes**:\n\n- Price vs. Capabilities\n- Ease of Use vs. Power\n- Horizontal vs. Vertical\n- Self-serve vs. Enterprise\n\n**Strategic insights**:\n\n- White space (underserved segments)\n- Crowded areas (avoid competing)\n- Movement over time (strategic direction)\n\n**Template**: `assets\u002Fpositioning-map-template.md`\n\nMultiple perceptual map formats, strategic analysis\n\n---\n\n## Battle Card Best Practices\n\n**Format**:\n\n- 1-2 pages maximum (quick reference)\n- Bullets, not paragraphs\n- Specific talk tracks (exact words)\n- Print-friendly\n\n**Content**:\n\n- Be honest about weaknesses (builds credibility)\n- Use customer language (outcomes, not features)\n- Include proof points (quotes, data, case studies)\n- Provide discovery questions (uncover advantages)\n\n**Maintenance**:\n\n- Update immediately on competitor changes\n- Monthly review, quarterly refresh\n- Sales feedback loop\n- Track win rates\n\n**Detailed guide**: `references\u002Fbattle-card-guide.md`\n\nCreating, training, maintenance, metrics\n\n---\n\n## Organizing Competitive Intelligence\n\n### Repository Structure\n\n```\n\u002FCompetitive Intelligence\n  \u002FCompetitor A\n    - Deep-dive analysis.md\n    - Battle card.md\n    - Product screenshots\u002F\n    - Reviews analysis.md\n  \u002FCompetitor B\n    [Same structure]\n  \u002FMarket Maps\n    - Positioning map.md\n    - Feature comparison.xlsx\n  \u002FWin-Loss Analysis\n    - Quarterly summaries\n```\n\n### Update Cadence\n\n**Continuous**: Monitor for major changes (Google Alerts, RSS)\n\n**Monthly**:\n\n- Scan competitor websites, blogs, changelogs\n- Read recent reviews\n- Update battle cards if needed\n\n**Quarterly**:\n\n- Deep-dive analysis refresh\n- Win\u002Floss review\n- Positioning assessment\n- Sales team competitive briefing\n\n**Detailed guide**: `references\u002Fcompetitive-intel-guide.md`\n\nMonitoring strategies, intelligence distribution\n\n---\n\n## Common Mistakes to Avoid\n\n**Feature parity obsession**:\n\n- Problem: Building everything competitors have\n- Fix: Focus on defensible differentiation\n\n**Outdated intelligence**:\n\n- Problem: Stale battle cards, wrong pricing\n- Fix: Regular update cadence, monitoring systems\n\n**Too comprehensive**:\n\n- Problem: 50-page analysis nobody reads\n- Fix: Right level of detail for audience (battle card vs. deep-dive)\n\n**Ignoring weaknesses**:\n\n- Problem: Only highlighting strengths\n- Fix: Honest assessment of trade-offs\n\n**Not using the intelligence**:\n\n- Problem: Analysis sits in drive, not actioned\n- Fix: Clear distribution, sales training, product impact\n\n---\n\n## For Solo Operators \u002F Small Teams\n\n**Simplified approach**:\n\n**Focus**: 2-3 most important competitors only\n\n**Monthly routine** (2-3 hours):\n\n- Check competitor websites for changes\n- Read 5-10 recent G2 reviews\n- Scan their blog\u002Fchangelog\n- Update battle card if needed\n\n**Quarterly deep-dive** (half day):\n\n- Full product trial\n- Read 20-30 reviews\n- Update positioning map\n- Refresh analysis doc\n\n**Templates to use**:\n\n- Battle card (1 page version)\n- Simplified positioning map\n- Lightweight deep-dive (key sections only)\n\n---\n\n## Templates and References\n\n### Assets (Ready-to-Use Templates)\n\nCopy-paste these for immediate use:\n\n- `assets\u002Fcompetitor-deep-dive-template.md` - Comprehensive competitive analysis\n- `assets\u002Fbattle-card-template.md` - Sales enablement quick reference\n- `assets\u002Fpositioning-map-template.md` - Strategic positioning & perceptual maps\n\n### References (Deep Dives)\n\nWhen you need comprehensive guidance:\n\n- `references\u002Fcompetitive-intel-guide.md` - Intelligence gathering, research, analysis\n- `references\u002Fbattle-card-guide.md` - Creating effective battle cards, sales enablement\n- `references\u002Fpositioning-guide.md` - Positioning frameworks, differentiation strategies\n\n---\n\n## Related Skills\n\n- `product-positioning` - Product positioning frameworks\n- `go-to-market-playbooks` - GTM and launch strategy\n- `roadmap-frameworks` - Product roadmaps\n- `market-sizing-frameworks` - Market opportunity assessment\n\n","# Competitive Analysis Templates\n\nTemplates for analyzing competitors, enabling sales teams, and defining strategic market positioning.\n\n## When to Use This Skill\n\n**Auto-loaded by agents**:\n\n- `market-analyst` - For competitor deep-dives, battle cards, and positioning maps\n\n**Use when you need**:\n\n- Analyzing competitor strategies and offerings\n- Creating sales battle cards\n- Building feature comparison matrices\n- Tracking competitive intelligence\n- Conducting win\u002Floss analysis\n- Defining differentiation strategy\n- Monitoring competitive threats\n- Positioning against alternatives\n\n## What is Competitive Analysis?\n\nCompetitive analysis helps you:\n\n- **Understand** your market position and competitive landscape\n- **Identify** differentiation opportunities and white space\n- **Enable** sales teams to win competitive deals\n- **Inform** product roadmap and strategic decisions\n- **Monitor** competitive threats and market shifts\n\n**NOT**: Copying competitors or building feature parity\n**BUT**: Finding defensible differentiation and strategic positioning\n\n**Good competitive analysis**: Actionable, evidence-based, honest about trade-offs, regularly updated\n\n**Bad competitive analysis**: Feature lists without context, outdated, biased, not used by teams\n\n---\n\n## Evidence Standards\n\n**Core principle:** All competitive intelligence must be based on verifiable public sources. Strategic analysis and recommendations are core value, but factual claims require source attribution.\n\n**Research requirements:**\n\n1. **Use verifiable public sources**\n   - Competitor websites, product pages, and documentation\n   - Pricing pages (with URLs and date accessed)\n   - Review sites (G2, Capterra, TrustRadius) with specific review citations\n   - News articles, press releases, and public announcements\n   - Product demos, trials, and publicly available materials\n\n2. **Source attribution**\n   - Every claim about competitor features, pricing, or strategy must cite source\n   - Format: \"[Feature\u002FClaim] (Source: [URL], accessed [Date])\"\n   - Review quotes must cite specific review with link\n   - When multiple sources confirm: cite 2-3 representative sources\n\n3. **When data is unavailable**\n   - Explicitly note: \"[Pricing not publicly available]\", \"[Requires product trial]\"\n   - Never fabricate competitor information to complete analysis\n   - Recommend steps to gather missing data (demo request, trial signup)\n   - Note limitation in battle card or analysis\n\n4. **What you CANNOT do**\n   - Fabricate competitor features, pricing, or capabilities\n   - Invent user testimonials or review quotes\n   - Make up market share numbers or competitive statistics\n   - Create fictional customer case studies\n\n5. **What you SHOULD do (core value)**\n   - Provide strategic analysis of competitive landscape\n   - Identify differentiation opportunities based on research\n   - Recommend positioning strategy against competitors\n   - Guide battle card creation and sales enablement\n   - Teach competitive intelligence methodologies\n   - Help interpret competitive data for strategic decisions\n\n**When in doubt:** If public information is unavailable, note the limitation explicitly rather than inventing data. Your strategic expertise in competitive analysis and positioning is your primary value.\n\n---\n\n## Three Core Templates\n\n### 1. Competitor Deep-Dive Analysis\n\n**Purpose**: Comprehensive competitive intelligence for strategic decisions\n\n**Use when**:\n\n- Quarterly competitive reviews\n- Market entry planning\n- Product roadmap planning\n- Understanding new competitive threat\n- Executive briefings\n\n**Key sections**:\n\n- Company overview (size, funding, strategy)\n- Product analysis (features, UX, pricing)\n- Go-to-market strategy (sales, marketing)\n- SWOT analysis (strengths, weaknesses, opportunities, threats)\n- Customer intelligence (reviews, win\u002Floss)\n- Competitive response strategy\n\n**Template**: `assets\u002Fcompetitor-deep-dive-template.md`\n\nComplete template with all sections, example content, intelligence sources\n\n**Time investment**: 8-12 hours initial, 2-3 hours quarterly updates\n\n**Comprehensive guide**: `references\u002Fcompetitive-intel-guide.md`\n\nIntelligence gathering, research techniques, analysis frameworks, organizing intelligence\n\n---\n\n### 2. Battle Card (Sales Enablement)\n\n**Purpose**: Quick-reference competitive enablement for sales teams\n\n**Use when**:\n\n- Sales team faces competitor regularly\n- New competitive threat emerges\n- Need to improve win rates vs. specific competitor\n- Onboarding new sales reps\n\n**Key sections**:\n\n- Quick stats (foundational context)\n- When you'll face them (common scenarios)\n- Where we win (strengths with proof)\n- Where they win (their strengths + how to counter)\n- Common objections & responses\n- Discovery questions (uncover our advantages)\n- Proof points (customer stories, data)\n\n**Template**: `assets\u002Fbattle-card-template.md`\n\nSales-ready format, specific talk tracks, objection handling, proof points\n\n**Format**: 1-2 pages maximum (quick reference for calls)\n\n**Update frequency**: Immediately on competitor changes, monthly review\n\n**Comprehensive guide**: `references\u002Fbattle-card-guide.md`\n\nCreating effective battle cards, sales enablement, training, maintenance, metrics\n\n---\n\n### 3. Positioning & Perceptual Mapping\n\n**Purpose**: Strategic market positioning and visual competitive landscape\n\n**Use when**:\n\n- Strategic planning (annual\u002Fquarterly)\n- Defining product strategy\n- Finding market white space\n- Developing messaging\n- Repositioning product\n\n**Key sections**:\n\n- Perceptual maps (visual market positioning)\n- Positioning statement (April Dunford framework)\n- Differentiation matrix\n- Value proposition map (jobs, pains, gains)\n- Strategic positioning grid\n- Brand positioning\n- Messaging framework\n\n**Template**: `assets\u002Fpositioning-map-template.md`\n\nPerceptual mapping formats, positioning frameworks, differentiation analysis\n\n**Use cases**: Strategic planning, market entry, messaging development\n\n**Comprehensive guide**: `references\u002Fpositioning-guide.md`\n\nPositioning frameworks, differentiation strategies, perceptual mapping, repositioning\n\n---\n\n## Choosing the Right Template\n\n**For strategic planning** → Use all three:\n\n1. Deep-dive analysis (understand landscape)\n2. Positioning map (define your position)\n3. Battle cards (enable execution)\n\n**For sales enablement** → Battle cards:\n\n- Quick reference during calls\n- Specific talk tracks and counters\n- Updated frequently\n\n**For product strategy** → Deep-dive + Positioning:\n\n- Feature gap analysis\n- Market white space\n- Differentiation strategy\n\n**For one competitor** → Start with deep-dive, then battle card\n\n**For market overview** → Positioning map first (landscape), then selective deep-dives\n\n---\n\n## Competitive Intelligence Process\n\n### 1. Gather Intelligence\n\n**Primary sources**:\n\n- Competitor website, demos, trials\n- Customer reviews (G2, Capterra, TrustRadius)\n- Win\u002Floss interviews\n- Customer feedback\n\n**Secondary sources**:\n\n- Press releases, news\n- Job postings (strategic direction)\n- Social media, podcasts\n- Analyst reports\n\n**Source citation requirements:**\n\n- Document URL and access date for every source\n- Cite specific G2\u002FCapterra reviews with links for user quotes\n- Note when information is unavailable: \"[Pricing not public]\"\n- Never fabricate data to fill intelligence gaps\n- Recommend additional research steps for missing data\n\n**Detailed guide**: `references\u002Fcompetitive-intel-guide.md`\n\nResearch techniques, intelligence sources, ethical guidelines, source citation best practices\n\n---\n\n### 2. Analyze Patterns\n\n**Look for**:\n\n- Feature launch velocity (product strategy)\n- Market expansion signals\n- Pricing changes\n- Partnership announcements\n- Messaging shifts\n\n**Framework**: Use SWOT analysis\n\n- **Strengths**: What they do well (facts, evidence)\n- **Weaknesses**: Exploitable gaps (customer complaints, missing features)\n- **Opportunities** (for them): Anticipate their moves\n- **Threats** (to us): How they could hurt us\n\n---\n\n### 3. Act on Insights\n\n**Product decisions**:\n\n- Close critical gaps (table stakes)\n- Exploit weaknesses (differentiation)\n- Defend strengths (maintain advantage)\n\n**Positioning**:\n\n- Find defensible differentiation\n- Avoid head-to-head on their strengths\n- Position in category where you win\n\n**Sales enablement**:\n\n- Create battle cards (competitive situations)\n- Train on objection handling\n- Share win stories\n\n---\n\n## Positioning Frameworks\n\n### April Dunford's 5 Components\n\nWork through in this order:\n\n**1. Competitive Alternatives**: What would customers use if you didn't exist?\n\n**2. Unique Attributes**: What can you do that alternatives can't?\n\n**3. Value (Benefits)**: What do those unique attributes enable?\n\n**4. Target Customer**: Who cares most about that value?\n\n**5. Market Category**: What context makes your value obvious?\n\n**Example**:\n\n> For Series A B2B SaaS companies who need to scale pipeline without growing SDR headcount, [Product] is an AI-powered sales development platform that books 10x more qualified meetings. Unlike Salesforce which requires large SDR teams, we use AI to automate the entire top-of-funnel.\n\n**Complete framework**: `references\u002Fpositioning-guide.md`\n\nPositioning strategies, differentiation, perceptual mapping, validation\n\n---\n\n### Perceptual Mapping\n\n**Purpose**: Visualize competitive landscape, find white space\n\n**Common axes**:\n\n- Price vs. Capabilities\n- Ease of Use vs. Power\n- Horizontal vs. Vertical\n- Self-serve vs. Enterprise\n\n**Strategic insights**:\n\n- White space (underserved segments)\n- Crowded areas (avoid competing)\n- Movement over time (strategic direction)\n\n**Template**: `assets\u002Fpositioning-map-template.md`\n\nMultiple perceptual map formats, strategic analysis\n\n---\n\n## Battle Card Best Practices\n\n**Format**:\n\n- 1-2 pages maximum (quick reference)\n- Bullets, not paragraphs\n- Specific talk tracks (exact words)\n- Print-friendly\n\n**Content**:\n\n- Be honest about weaknesses (builds credibility)\n- Use customer language (outcomes, not features)\n- Include proof points (quotes, data, case studies)\n- Provide discovery questions (uncover advantages)\n\n**Maintenance**:\n\n- Update immediately on competitor changes\n- Monthly review, quarterly refresh\n- Sales feedback loop\n- Track win rates\n\n**Detailed guide**: `references\u002Fbattle-card-guide.md`\n\nCreating, training, maintenance, metrics\n\n---\n\n## Organizing Competitive Intelligence\n\n### Repository Structure\n\n```\n\u002FCompetitive Intelligence\n  \u002FCompetitor A\n    - Deep-dive analysis.md\n    - Battle card.md\n    - Product screenshots\u002F\n    - Reviews analysis.md\n  \u002FCompetitor B\n    [Same structure]\n  \u002FMarket Maps\n    - Positioning map.md\n    - Feature comparison.xlsx\n  \u002FWin-Loss Analysis\n    - Quarterly summaries\n```\n\n### Update Cadence\n\n**Continuous**: Monitor for major changes (Google Alerts, RSS)\n\n**Monthly**:\n\n- Scan competitor websites, blogs, changelogs\n- Read recent reviews\n- Update battle cards if needed\n\n**Quarterly**:\n\n- Deep-dive analysis refresh\n- Win\u002Floss review\n- Positioning assessment\n- Sales team competitive briefing\n\n**Detailed guide**: `references\u002Fcompetitive-intel-guide.md`\n\nMonitoring strategies, intelligence distribution\n\n---\n\n## Common Mistakes to Avoid\n\n**Feature parity obsession**:\n\n- Problem: Building everything competitors have\n- Fix: Focus on defensible differentiation\n\n**Outdated intelligence**:\n\n- Problem: Stale battle cards, wrong pricing\n- Fix: Regular update cadence, monitoring systems\n\n**Too comprehensive**:\n\n- Problem: 50-page analysis nobody reads\n- Fix: Right level of detail for audience (battle card vs. deep-dive)\n\n**Ignoring weaknesses**:\n\n- Problem: Only highlighting strengths\n- Fix: Honest assessment of trade-offs\n\n**Not using the intelligence**:\n\n- Problem: Analysis sits in drive, not actioned\n- Fix: Clear distribution, sales training, product impact\n\n---\n\n## For Solo Operators \u002F Small Teams\n\n**Simplified approach**:\n\n**Focus**: 2-3 most important competitors only\n\n**Monthly routine** (2-3 hours):\n\n- Check competitor websites for changes\n- Read 5-10 recent G2 reviews\n- Scan their blog\u002Fchangelog\n- Update battle card if needed\n\n**Quarterly deep-dive** (half day):\n\n- Full product trial\n- Read 20-30 reviews\n- Update positioning map\n- Refresh analysis doc\n\n**Templates to use**:\n\n- Battle card (1 page version)\n- Simplified positioning map\n- Lightweight deep-dive (key sections only)\n\n---\n\n## Templates and References\n\n### Assets (Ready-to-Use Templates)\n\nCopy-paste these for immediate use:\n\n- `assets\u002Fcompetitor-deep-dive-template.md` - Comprehensive competitive analysis\n- `assets\u002Fbattle-card-template.md` - Sales enablement quick reference\n- `assets\u002Fpositioning-map-template.md` - Strategic positioning & perceptual maps\n\n### References (Deep Dives)\n\nWhen you need comprehensive guidance:\n\n- `references\u002Fcompetitive-intel-guide.md` - Intelligence gathering, research, analysis\n- `references\u002Fbattle-card-guide.md` - Creating effective battle cards, sales enablement\n- `references\u002Fpositioning-guide.md` - Positioning frameworks, differentiation strategies\n\n---\n\n## Related Skills\n\n- `product-positioning` - Product positioning frameworks\n- `go-to-market-playbooks` - GTM and launch strategy\n- `roadmap-frameworks` - Product roadmaps\n- `market-sizing-frameworks` - Market opportunity assessment\n\n",{"name":5,"description":7},"main","a4b48842f3e48549adf3dc335a8837c66da99497","agents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates",0,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng","2026-05-17 16:00:01",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill competitive-analysis-templates",{"tool":36,"command":37},"bunx","bunx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill competitive-analysis-templates",{"tool":39,"command":40},"pnpm","pnpm dlx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill competitive-analysis-templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002FSKILL.md",true,[44,50,54,58,64,68],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"assets\u002Fbattle-card-template.md","ASSET","资产文件",5788,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002Fassets\u002Fbattle-card-template.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"assets\u002Fcompetitor-deep-dive-template.md",8142,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002Fassets\u002Fcompetitor-deep-dive-template.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Fpositioning-map-template.md",7577,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002Fassets\u002Fpositioning-map-template.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fbattle-card-guide.md","REFERENCE","参考文档",8076,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002Freferences\u002Fbattle-card-guide.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcompetitive-intel-guide.md",7203,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002Freferences\u002Fcompetitive-intel-guide.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fpositioning-guide.md",10160,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fai-pm-copilot\u002Fskills\u002Fcompetitive-analysis-templates\u002Freferences\u002Fpositioning-guide.md",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72ZGWW03JSE1T3TKK5NZ11Y","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72ZGT3FJT7QRM1VNQRKR0XD","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M72ZGQ69DCF0SBP9JXFPWKJS","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M72ZGNF126QT0MQ2D3DNGZRN","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M72ZGHVJ9S0YXMNBHQGQ95BY","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M72ZGFNZCHFY2FS3ZD9MCYV9","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]