Purpose
Turn scattered pipeline data, clinical trial registry entries, and published readouts into a single structured competitive map for a therapeutic area or mechanism of action — surfacing where the field is crowded, where differentiation is defensible, and what those signals mean for development strategy. Eliminates the weeks-long manual synthesis that precedes portfolio, indication, and business development decisions.
When to Use
Invoke this skill when the user asks to:
- Map the competitive landscape for a specific therapeutic area or indication
- Assess how crowded a mechanism of action is and whether differentiation is possible
- Build a competitive briefing for a portfolio prioritization or go/no-go decision
- Evaluate an in-licensing or acquisition target against the surrounding field
- Identify whitespace or unmet need gaps a program could occupy
- Compare a candidate asset's positioning against named competitors by phase
Inputs Required
Before starting, collect:
- Therapeutic area / indication: The disease or patient population in scope
- Mechanism of action: The target, pathway, or modality being analyzed (or "all mechanisms" if landscape-wide)
- Assets/competitors known: Any specific programs, companies, or trial registry IDs the user already has
- Own asset context: The user's candidate profile (mechanism, phase, differentiation hypothesis) — or "external scan only"
- Development stage focus: Preclinical / Phase 1 / Phase 2 / Phase 3 / Approved — or full pipeline
- Decision the analysis feeds: Portfolio prioritization, BD evaluation, indication selection, or competitive briefing
- Geographic scope: Global / US / EU / specific regions for regulatory and commercial context
If mechanism focus is missing, default to a full-mechanism landscape scan. If own-asset context is missing, produce an external competitive map and note that differentiation is framed against the field rather than a specific candidate.
Instructions
Step 1: Landscape Scope and Framing
Establish the boundaries of the analysis before mapping.
- Confirm the indication definition (including line of therapy and patient sub-populations, since these fragment competition)
- Define which mechanisms are in scope — same-target competitors, same-pathway competitors, and modality-agnostic competitors for the same clinical endpoint
- State the analytical cutoff: what counts as a competitor (e.g., programs in active development for the same indication and comparable endpoint)
- Flag any known data gaps (undisclosed mechanisms, stealth programs, discontinued assets) so the map's confidence is transparent
Step 2: Pipeline Mapping by Phase
Organize every identified competitor into a phase-by-phase competitive map.
For each asset, capture:
- Asset / program name
- Sponsor (company or institution)
- Mechanism / modality (target, pathway, format — e.g., small molecule, mAb, bispecific, ADC, cell/gene therapy)
- Development phase and most advanced indication
- Key differentiator or positioning claim (as stated by the sponsor or inferred from design)
- Latest catalyst (data readout, regulatory milestone, or expected event)
Group the map into: Approved / Filed, Phase 3, Phase 2, Phase 1, Preclinical / Discovery. Present as a table when the asset count exceeds five.
Step 3: Mechanism Differentiation Analysis
Assess where the mechanism space is crowded versus open.
- Crowding assessment: Count active programs per mechanism class; label each class as Saturated (5+ clinical programs), Contested (2–4), or Emerging (0–1)
- Differentiation axes: For the mechanism in focus, evaluate defensible differentiation across efficacy hypothesis, safety/tolerability, dosing/route, patient sub-population, combinability, and durability
- Fast-follower risk: Identify whether the mechanism is being validated by a leader (de-risked but competitive) or is first-in-class (higher risk, higher whitespace)
- Modality shift signals: Note whether the field is migrating toward newer modalities (e.g., small molecule → biologic → cell therapy) that could obsolete an incumbent approach
Step 4: Clinical Trial Design Signals
Read competitor trial design as strategic intelligence.
- Endpoint choices: What primary endpoints are competitors using, and does convergence signal a de facto regulatory standard?
- Patient enrichment: Are competitors selecting biomarker-defined or line-of-therapy sub-populations — and does that reveal where they see the winnable segment?
- Comparator arms: Standard of care vs. placebo vs. active competitor — signals confidence and regulatory positioning
- Enrollment velocity and site footprint: Fast enrollment or broad geography signals conviction and resource commitment
- Adaptive or seamless designs: Signals speed-to-market intent worth factoring into competitive timing
Step 5: Unmet Need and Whitespace Identification
Locate the gaps the field has not yet filled.
- Map current standard of care against residual unmet need (efficacy ceiling, safety burden, delivery inconvenience, non-responder populations)
- Identify patient sub-populations, lines of therapy, or endpoints that no active program is prioritizing
- Distinguish true whitespace (unaddressed medical need) from vacated whitespace (abandoned because prior programs failed — a warning, not an opportunity)
- Rank whitespace opportunities by attractiveness (size of gap) and feasibility (biological tractability, regulatory precedent)
Step 6: Competitive Positioning Verdict
Place the field on a positioning frame.
- Classify the overall landscape: First-in-class race / Best-in-class contest / Crowded me-too / Fragmenting by sub-population
- If own-asset context was provided, position the candidate explicitly: where it leads, where it trails, and its most defensible differentiation claim
- Identify the 2–3 competitors that matter most for planning and why (nearest phase, most similar mechanism, strongest data)
Step 7: Development Strategy Implications
Translate the map into decisions the buyer can act on.
- Timing: Is there a first-mover window, or is fast-follow the realistic play given phase gaps?
- Indication strategy: Should the program target the crowded lead indication or a differentiated sub-population / line of therapy?
- Trial design recommendations: Endpoint, comparator, and enrichment choices that create separation from the field
- Differentiation thesis: The single most defensible claim the program should build its development plan around
- Watch list: The specific competitor catalysts (readouts, filings) that would change this strategy
- Recommendation: One clear strategic call (advance / reposition / deprioritize / license) with rationale
Output Format
- Structure: Seven sections following the diagnostic sequence; pipeline map as a phase-grouped table; whitespace and implications as ranked bullets
- Length: 1,100–1,500 words
- Format: Structured intelligence briefing — tables for the pipeline map and crowding assessment, prose for analysis, bulleted implications
- Sections: Landscape scope → Pipeline map by phase → Mechanism differentiation → Trial design signals → Whitespace → Positioning verdict → Development strategy implications
- Tone: R&D strategy director — analytical, evidence-anchored, decision-oriented; states confidence levels and flags data gaps rather than overclaiming
Quality Checklist
Before delivering output, verify:
- [ ] Every competitor asset is placed in a specific phase bucket with sponsor and mechanism named
- [ ] Mechanism crowding is quantified with a program count and a labeled tier (Saturated / Contested / Emerging)
- [ ] Whitespace items distinguish true unaddressed need from vacated/failed whitespace
- [ ] Trial design section reads at least two competitor design choices as strategic signals — not just lists endpoints
- [ ] Development implications include a single defensible differentiation thesis, not a menu of options
- [ ] A named watch list of specific competitor catalysts is provided
- [ ] Data gaps and confidence limits are explicitly stated where evidence is incomplete
Notes
- The highest-value output is often the whitespace section — but vacated whitespace (indications where prior programs failed) is a trap, not an opportunity; always investigate why a gap exists before recommending it
- Trial design convergence is a strong signal of an emerging regulatory standard; a program that ignores the de facto endpoint the field is validating risks a non-registrable dataset
- When source data is thin (stealth programs, undisclosed mechanisms), state the limitation and provide a conservative estimate rather than a confident number — the buyer is making capital-allocation decisions on this map
- If the user provides trial registry IDs or a specific competitor list, anchor the analysis to those first, then expand to the broader field
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills