plugins/workflow/skills/market-context/SKILL.md
Use when validating market timing, structural forces, or distribution moats before committing strategic resources—focuses on macro context, not individual competitor teardowns.
npx skillsauth add joellewis/skill-library market-contextInstall 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.
Market context is the forensic analysis of structural forces—timing, distribution moats, and demand aggregation—that determine whether a product can capture long-term value. This skill prevents "Strategy Blindness" by forcing an audit of the "Where to Play" domains before any resources are allocated.
NO STRATEGIC RECOMMENDATION WITHOUT VALIDATED MARKET CONTEXT
Assumed market dynamics are the primary cause of high-growth failures. Every claim must be validated against current structural shifts (e.g., Aggregation Theory or Unbundling).
digraph market_context_flow {
"Start" [shape=doublecircle];
"Step 1: Structural Audit" [shape=box];
"Step 2: 0-to-1 Timing Check" [shape=diamond];
"Step 3: Distribution Audit" [shape=box];
"Step 4: Context Validation" [shape=diamond];
"Done" [shape=doublecircle];
"Start" -> "Step 1: Structural Audit";
"Step 1: Structural Audit" -> "Step 2: 0-to-1 Timing Check";
"Step 2: 0-to-1 Timing Check" -> "Step 3: Distribution Audit" [label="timing right"];
"Step 2: 0-to-1 Timing Check" -> "Step 1: Structural Audit" [label="too early/late"];
"Step 3: Distribution Audit" -> "Step 4: Context Validation";
"Step 4: Context Validation" -> "Done" [label="context validated"];
"Step 4: Context Validation" -> "Step 1: Structural Audit" [label="gaps in logic"];
}
Evaluate if the industry is structurally attractive. (Source: Lafley, Playing to Win, Ch. 3)
Validate the context against Thiel's fundamental laws. (Source: Thiel, Zero to One, Ch. 13)
Shift from product-centricity to distribution-centricity. (Source: Gil, High Growth Handbook, Intro)
State what must be true about the market for the strategy to work. (Source: Lafley, Ch. 7)
problem-framing — You cannot define a market without defining the problem first.competitive-analysis — To identify if you are competing in a "Red Ocean."strategy-clarity — To ensure the context matches the winning aspiration.| Thought | Reality | |---------|---------| | "The market is so big, we only need 1%." | The 1% Trap leads to zero share. Successful firms start small and monopolize. | | "Our product is so good, it sells itself." | Distribution is at least as important as product. (Source: Gil/Thiel). | | "We are first to market." | First mover is a tactic; Last Mover is the goal (Far-future profts). | | "The industry is too old to change." | Old industries are prime for "Unbundling" or "Aggregation." (Source: Stratechery). | | "First mover advantage will protect us." | First Mover is a tactic, not a moat. Last Mover Advantage — generating the last great development and capturing durable profits — is the strategic goal. (Source: Thiel, Zero to One, Ch. 5) | | "We're debating whether this is Custom or Product." | Evolution stage is observable: how many vendors? Published standards? Training courses? These are empirical signals. If you're debating, look at the market, not your org chart. | | "Supply is commoditizing but that's not our problem." | When supply-side components commoditize, aggregation dynamics form on the demand side. This directly affects your Where to Play. (Source: Stratechery, "Aggregation Theory"; Wardley, Wardley Maps, Ch. 4) |
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.