competitive-strategist
Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.
What this skill does
# Competitive Strategist
Expert competitive intelligence and positioning guidance for winning in crowded markets — from research methodologies to sales enablement and everything in between.
## Philosophy
Competitive strategy isn't about copying competitors or tearing them down:
1. **Know yourself first** — You can't position against others until you know your own strengths
2. **Focus on customers, not competitors** — What they need matters more than what rivals do
3. **Be honest** — Lies and FUD destroy credibility faster than any competitor
4. **Stay current** — Markets move fast; stale intel costs deals
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `research-*` — Competitive research methodologies and intelligence gathering
- `analysis-*` — Win/loss analysis and market landscape mapping
- `battlecard-*` — Battlecard creation, structure, and maintenance
- `positioning-*` — Positioning against alternatives and differentiation
- `messaging-*` — Competitive messaging and objection handling
- `enablement-*` — Sales enablement for competitive situations
- `monitoring-*` — Competitive monitoring systems and alerts
## Core Frameworks
### The Competitive Intelligence Cycle
```
┌─────────────────────────────────────────────────────────────┐
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ GATHER │───▶│ ANALYZE │───▶│ SHARE │ │
│ │ (Intel) │ │ (Insight)│ │ (Enable) │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ▲ │ │
│ │ ┌──────────┐ │ │
│ └──────────│ UPDATE │◀─────────┘ │
│ │ (Iterate)│ │
│ └──────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
```
### Competitive Positioning Matrix
| Positioning Type | When to Use | Key Approach |
|------------------|-------------|--------------|
| **Head-to-head** | You're stronger on key dimensions | Direct comparison |
| **Niche down** | Competitor owns general category | Own a specific segment |
| **Reframe** | Competitor's strength is irrelevant | Change the criteria |
| **Leapfrog** | New capability they can't match | Future-oriented vision |
| **Coexist** | Different jobs to be done | Complement, don't compete |
### Competitor Tiers
| Tier | Description | Monitoring Frequency | Depth of Analysis |
|------|-------------|---------------------|-------------------|
| **Primary** | Direct competitors, same ICP | Weekly | Deep battlecards |
| **Secondary** | Adjacent solutions, partial overlap | Monthly | Overview cards |
| **Emerging** | Startups, potential disruptors | Quarterly | Watch list |
| **Alternatives** | Status quo, DIY, spreadsheets | Ongoing | Pain point mapping |
### Win/Loss Analysis Framework
```
Deal Outcome
│
├── Won Against Competitor
│ ├── What differentiated us?
│ ├── What did they say about competitor?
│ └── What would have changed their mind?
│
└── Lost to Competitor
├── What was the deciding factor?
├── Where did we fall short?
└── What could we have done differently?
```
### The Battlecard Structure
| Section | Purpose | Update Frequency |
|---------|---------|------------------|
| **Overview** | Quick context, what they do | Quarterly |
| **Positioning** | How we win, key differentiators | Monthly |
| **Landmines** | Questions to ask that expose weaknesses | As discovered |
| **Objection Handling** | Responses to "Why not [competitor]?" | As encountered |
| **Proof Points** | Customer quotes, case studies | As available |
| **Pricing Intel** | Known pricing, packaging | As discovered |
## Competitive Response Spectrum
| Situation | Response | Example |
|-----------|----------|---------|
| **They launch feature you have** | Emphasize experience, depth | "We've had this for 2 years, here's what we've learned" |
| **They launch feature you don't** | Roadmap or reframe | "We're focused on X because customers told us Y matters more" |
| **They cut price** | Hold on value | "You get what you pay for — here's the TCO comparison" |
| **They spread FUD** | Correct with facts | "That's not accurate — here's the truth with proof" |
| **They announce funding** | Ignore or pivot to stability | "We've been profitable since 2019" |
## Intelligence Sources (Ranked by Value)
1. **Win/loss interviews** — First-party, high signal
2. **Sales call recordings** — Real objections, real context
3. **Customer feedback** — Why they chose you (and considered others)
4. **G2/Capterra reviews** — Volume of sentiment data
5. **LinkedIn activity** — Hiring, messaging, customer posts
6. **Job postings** — Strategic direction signals
7. **Press/funding news** — Major moves, positioning shifts
8. **Product trials** — Hands-on intel (respect ToS)
## Anti-Patterns
- **FUD tactics** — Spreading fear, uncertainty, doubt backfires
- **Obsessing over competitors** — Customer needs > competitor moves
- **Stale battlecards** — Outdated intel loses deals
- **One-size-fits-all** — Different competitors need different strategies
- **Ignoring the real competitor** — Often it's "do nothing" or spreadsheets
- **Attacking instead of differentiating** — Negative selling repels buyers
- **Hoarding intel** — Unshared intelligence is worthless
- **Copying competitors** — You become undifferentiated
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.