From fieldwork
Triggers when the user wants to understand the competitive landscape - what alternatives exist, how they're positioned, where the gaps are, and what this means for the product. Also triggers if the user says 'competitive analysis', 'what are competitors doing', 'how do we compare', or 'who else does this'. Can run standalone or feed into discover, write-spec, or write-gtm.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fieldwork:analyse-competitorsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Understand the competitive landscape well enough to make sharper product decisions. This is not a feature comparison matrix - it is an analysis of how competitors frame the problem, who they're built for, and where they fall short. The output feeds directly into positioning, opportunity framing, and GTM.
Understand the competitive landscape well enough to make sharper product decisions. This is not a feature comparison matrix - it is an analysis of how competitors frame the problem, who they're built for, and where they fall short. The output feeds directly into positioning, opportunity framing, and GTM.
Announce at start: "I'm using the Fieldwork analyse-competitors skill to map the competitive landscape."
Use when:
Do NOT use when:
context/product-context.md - read the Competitors section. What's already known?outputs/opportunities/{feature-name}/opportunity.mdList every realistic alternative a user might choose instead of this product for this specific problem. Include:
Do not limit to named competitors. "Spreadsheet + email" is a competitor.
For each competitor, answer:
Keep each analysis tight. Three sentences per dimension is enough.
After analysing all alternatives, ask:
These gaps are where differentiation lives.
Ask: "Which competitor is most likely to eat into this product's position in the next 12 months, and why?"
This is the competitive risk. It belongs in the GTM plan and in context/constraints.md.
Based on the gap analysis, suggest 1-3 positioning angles that are:
Save to outputs/competitive/{analysis-name}/competitive-analysis.md.
Update context/product-context.md Competitors section - append new findings, do not rewrite.
If connected to an opportunity: note competitive context in outputs/opportunities/{feature-name}/opportunity.md under a "Competitive context" section.
---
analysis: {analysis-name}
date: YYYY-MM-DD
context: [discovery | gtm | standalone | competitor-move]
linked-opportunity: outputs/opportunities/{feature-name}/opportunity.md (if exists)
---
# Competitive Analysis: {Analysis Name}
## Scope
[What problem or opportunity this analysis covers - one sentence]
## Alternatives map
### [Competitor / Alternative name]
- **Built for:** [Who it actually serves]
- **Wins at:** [Where it genuinely beats alternatives]
- **Falls short:** [Specific gaps]
- **Positioning:** [How it describes itself]
- **Pricing:** [Model and rough tier]
- **User signal:** [What users say - reviews, complaints, praise]
_(repeat for each alternative)_
## The "do nothing" option
[What users do today without any tool - manual process, workaround, or just living with the problem]
## Gaps
[What nobody is solving well - specific, not generic]
## Competitive threat
[Which competitor is most likely to move into this space, and what that looks like]
## Positioning implications
[1-3 angles that are defensible, user-grounded, and unclaimed]
## Recommended next step
[Feed into discover / update GTM positioning / note as constraint / monitor and revisit]
"Competitive analysis saved to outputs/competitive/{analysis-name}/competitive-analysis.md.
context/product-context.md updated with new competitive context.
[If connected to opportunity]: Competitive framing added to opportunity.md.
The clearest gap is: [gap]. The strongest positioning angle is: [angle].
[Route based on context]:
discover using this competitive framing?'npx claudepluginhub jklazinga/fieldwork --plugin fieldworkMap existing solutions, alternatives, and competitive positioning to understand the problem space.
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
Conducts competitive product analysis to deliver positioning calls: where to play, how to win. Use for competitor analysis, landscape mapping, or comparison queries.