skills/competitor-analysis/SKILL.md
Analyze competitive landscape with feature matrices, positioning maps, and strategic gap analysis. Use when asked to analyze competitors, map the competitive landscape, find differentiation, or evaluate alternatives to a product.
npx skillsauth add assimovt/productskills competitor-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Analyze competitors to find positioning gaps, not to copy features. The goal is to understand where alternatives fail your ICP so you can win on what matters to them.
List every alternative your ICP considers. Three categories:
Build a comparison table focused on what YOUR ICP cares about, not every feature that exists.
| Capability | Your Product | Competitor A | Competitor B | Manual Workaround | |---|---|---|---|---| | [ICP-relevant capability] | How you do it | How they do it | How they do it | How people hack it |
Rate each: Strong / Adequate / Weak / Missing. Don't use checkmarks — they hide nuance. Include pricing model in the matrix — it constrains product decisions.
Example row: | Real-time collaboration | Strong (live cursors) | Weak (polling-based) | Missing | Google Docs + Slack — Adequate | So what: Their users are duct-taping two tools; our strength is their pain point.
Plot competitors on two axes that matter to your ICP. Choose axes where you can credibly win at least one.
Common axis pairs:
The empty quadrant is your opportunity. If no quadrant is empty, you need a different framing.
Example (project management tools, ICP = small remote teams):
Powerful
|
Jira ------+------ Linear
|
Easy ----------------+---------------- Hard
|
Trello -----------+------ Asana
|
Simple
Empty quadrant: Powerful + Easy. That's the opportunity.
For each competitor, answer:
Skills from productskills.
development
Prepare and conduct user interviews that extract truth, not validation. Use when asked to create an interview guide, prepare for user interviews, plan customer discovery, or talk to users. Built on The Mom Test and YC's Five Questions framework for startup customer development.
documentation
Write product strategy documents with real tradeoffs and clear choices. Use when asked to write a product strategy, define strategic direction, create a strategy doc, or articulate where to play and how to win. Built on Playing to Win and Rumelt's Strategy Kernel.
tools
Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.
development
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.