plugins/workflow/skills/competitive-analysis/SKILL.md
Use when performing a structured teardown of a specific competitor's activity system, moat, or vulnerability profile—requires at least one named rival to analyze.
npx skillsauth add joellewis/skill-library competitive-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.
Competitive analysis is not a list of features; it is a forensic audit of a rival's "Activity System" to find where their internal logic is brittle. This skill prevents the "Arrogance Trap" identified in the GE and Boeing collapses by forcing an evidence-based assessment of moats and vulnerabilities.
NO COMPETITIVE CLAIM WITHOUT EVIDENCE FROM AT LEAST TWO INDEPENDENT SOURCES
Unverified claims about being "10x better" or having "no competitors" are the primary signals of impending strategic failure.
digraph competitive_analysis_flow {
"Start" [shape=doublecircle];
"Step 1: Activity Mapping" [shape=box];
"Gate: Moat Audit" [shape=diamond];
"Step 3: Vulnerability Check" [shape=box];
"Step 4: Evidence Gate" [shape=diamond];
"Done" [shape=doublecircle];
"Start" -> "Step 1: Activity Mapping";
"Step 1: Activity Mapping" -> "Gate: Moat Audit";
"Gate: Moat Audit" -> "Step 3: Vulnerability Check" [label="moat verified"];
"Gate: Moat Audit" -> "Step 1: Activity Mapping" [label="unclear value"];
"Step 3: Vulnerability Check" -> "Step 4: Evidence Gate";
"Step 4: Evidence Gate" -> "Done" [label="2+ sources found"];
"Step 4: Evidence Gate" -> "Step 3: Vulnerability Check" [label="hearsay only"];
}
problem-framing instead).Do not compare features. Compare the system of reinforcing activities. (Source: Lafley, Playing to Win, Ch. 5)
Assess whether the competitor (or you) has a durable power source. Use Helmer's 7 Powers as the primary taxonomy, with Thiel's 10x test as the threshold bar. (Source: Helmer, 7 Powers; Thiel, Zero to One, Ch. 5)
For each power source identified, apply Thiel's threshold: is it 10x better on a dimension that matters to the customer, or is it a marginal advantage that can be competed away?
Assess the rival's execution discipline. (Source: Davis, Lessons from the Titans, Ch. 12)
For every claim (e.g., "We are faster"), you must cite:
problem-framing — You cannot analyze competitors without knowing the "Job-to-be-Done."devils-advocate — Use this to find the flaws in your own competitive claims.strategy-clarity — To ensure your "How to Win" is distinct from the rival's activity system.| Thought | Reality | |---------|---------| | "We have no competitors." | You are defining the market too narrowly. Anything the customer uses to solve the problem is a competitor. | | "Our tech is 10x better." | Unless it's 10x better on an unmeasurable consumer attribute (UX), it's a "modular" target. | | "They are just a copycat." | "Me-too" competitors with lower overhead or a "modular" stack often win on price (Modular Disruption). | | "We don't need evidence for common knowledge." | Common knowledge is often "arrogance in disguise." Verification is the only defense. | | "They can't respond without destroying their business." | Verify the direction: Counter-Positioning only applies when their response requires self-harm. If you can't respond to them, you're the one being Counter-Positioned. | | "We have no competitors." | Anything the customer uses to solve the job — including doing nothing — is a competitor. You defined the market wrong. (Source: Thiel, Zero to One, Ch. 5) |
These thoughts mean STOP — you are about to shortcut:
databases
Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignment, and conflict-resolution protocol.
development
Use when you need to map who has power, who will be affected, and what motivates each party — produces a stakeholder map as an analytical artifact. This skill identifies and categorizes stakeholders; it does not persuade or influence them (use influence-architect for that).
testing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
testing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.