agentleFS
nisarthnisarth/claude-skills-store/skills/product-management/competitive-brief/SKILL.md

competitive-brief

Skill1 starsChanged 7 months agoMITView on GitHub

Create a competitive analysis brief for one or more competitors or a feature area. Use when informing product strategy or feature prioritization, building sales battle cards, prepping board or investor materials, or deciding where to differentiate vs. match. Trigger phrases: "competitive analysis", "competitor comparison", "how do we compare to", "battle card for", "competitive landscape", "what is X doing", "feature comparison", "competitive brief on", "analyze our competitors", "positioning vs"

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create structured competitive analysis briefs that inform product strategy, sales positioning, and executive decision-making.

    line 12
  2. Distinctive:

    If the user provides a competitor name without context, ask: "What dimension matters most right now -- are you trying to win deals against …

    line 25
  3. Distinctive:

    Use: Full / Partial / Beta / None / Unknown.

    line 53
  4. Distinctive:

    Place competitors on two axes most relevant to the market:

    line 57
  5. Distinctive:

    Keep to one page per competitor

    line 138

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Competitive Analysis Brief

Create structured competitive analysis briefs that inform product strategy, sales positioning, and executive decision-making. Compare features, pricing, positioning, strengths, and weaknesses.

Workflow

Step 1: Scope the Analysis

Clarify before starting:

  1. Competitors: Which specific companies or products? Limit to 2-4 for depth.
  2. Dimensions: Features, pricing, positioning, GTM, or all of the above?
  3. Audience: Sales team (battle card), exec team (strategic), or product team (tactical)?
  4. Your product: What is your current positioning and key differentiators?

If the user provides a competitor name without context, ask: "What dimension matters most right now -- are you trying to win deals against them, decide what to build next, or understand their strategy?"

Step 2: Gather Intelligence

For each competitor, collect across these categories:

CategoryWhat to Capture
ProductCore features, recent launches, platform/integrations, UX approach
PositioningTagline, target persona, key messaging, value prop
PricingModel (per-seat, usage, flat), tiers, published pricing, free tier
GTMSales motion (PLG, sales-led, hybrid), channels, partnerships
StrengthsWhat they do better than you or the market
WeaknessesWhere they fall short, common complaints, gaps
TrajectoryFunding, hiring patterns, recent announcements, strategic direction

Sources to check: product pages, pricing pages, changelog/release notes, G2/Capterra reviews, job postings, press releases, analyst reports.

Step 3: Build the Comparison

Feature Matrix

FeatureYour ProductCompetitor ACompetitor B
[Feature 1]FullPartialNone
[Feature 2]PartialFullFull
[Feature 3]NoneFullPartial

Use: Full / Partial / Beta / None / Unknown. Add brief notes for nuance.

Positioning Map

Place competitors on two axes most relevant to the market:

                    Enterprise-grade
                         |
           [Comp B]      |      [You]
                         |
  Simple ----------------+---------------- Powerful
                         |
           [Comp C]      |      [Comp A]
                         |
                    SMB-focused

Choose axes that reveal strategic gaps, not ones where everyone clusters.

Pricing Comparison

Your ProductCompetitor ACompetitor B
Free tierYes/NoYes/NoYes/No
Entry price$/mo$/mo$/mo
Mid-tier$/mo$/mo$/mo
EnterpriseCustomCustomCustom
ModelPer-seatUsageFlat

Step 4: Derive Insights

For each competitor, write:

### [Competitor Name]

**In one sentence**: [What they are and who they serve]

**Where they win**: [1-2 specific areas where they outperform you]

**Where they lose**: [1-2 specific areas where they fall short]

**Their bet**: [The strategic direction they are pursuing]

**Your response**: [What you should do about it -- match, differentiate, or ignore]

Step 5: Compile the Brief

## Competitive Analysis: [Topic/Area]
Date: [Date] | Author: [Name]

### Executive Summary
[3-5 sentences: market landscape, your position, key takeaway]

### Competitor Profiles
[One section per competitor]

### Feature Comparison
[Matrix]

### Positioning Map
[2x2 or narrative]

### Pricing Landscape
[Comparison table]

### Strategic Implications
1. [Where to differentiate]
2. [Where to match / reach parity]
3. [Where to ignore]

### Recommendations
- [Action 1]: [Rationale]
- [Action 2]: [Rationale]
- [Action 3]: [Rationale]

Output Variants

For sales teams (battle card):

  • Lead with objection handling and win/loss talking points
  • Include "When they say X, we say Y" scripts
  • Keep to one page per competitor

For executives:

  • Lead with strategic implications and market dynamics
  • Include market share estimates and trajectory
  • Focus on where to invest vs. divest

For product teams:

  • Lead with feature gaps and parity requirements
  • Include user experience comparisons
  • Map to roadmap decisions

Examples

Example 1: Direct Competitor

User: "Create a competitive brief on Notion vs. our wiki product." Response: Compare along documentation, collaboration, integrations, pricing, and enterprise readiness. Highlight where Notion's flexibility is a strength (customization) and weakness (lack of structure for large teams).

Example 2: Feature Area

User: "How does our AI feature compare to competitors?" Response: Build a feature matrix of AI capabilities across 3-4 competitors. Note which are shipping AI as core vs. add-on, pricing implications, and user reception from review sites.

Example 3: Market Entry

User: "We're entering the analytics space. Who are we up against?" Response: Map the competitive landscape by segment (enterprise vs. SMB, technical vs. business user). Identify the most and least crowded positions. Recommend a positioning angle.

Best Practices

  1. Be specific, not generic. "Their search is faster" is useless. "Their search returns results in <200ms with typo tolerance; ours takes 1-2s without" is actionable.
  2. Separate fact from opinion. Label what is verified (pricing page, product demo) vs. inferred (strategy, roadmap).
  3. Update regularly. Competitive landscapes shift. Note the date of analysis and flag areas likely to change.
  4. Include your weaknesses. The brief loses credibility if it only highlights where you win. Honest assessment drives better strategy.
  5. Focus on what matters to customers. Competitors may have 50 features you lack, but only 3 matter to your buyers.
  6. Check G2 and Capterra reviews. Real user complaints reveal weaknesses that marketing hides.
  7. Watch their job postings. Hiring patterns reveal strategic direction 6-12 months before product launches.
  8. Talk to churned customers. Users who left you for a competitor (or vice versa) are the best source of competitive insight.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.