Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From discovery
Document and prioritize the assumptions underlying your product strategy before validation.
npx claudepluginhub sethdford/claude-skills --plugin pm-discoveryHow this skill is triggered — by the user, by Claude, or both
Slash command
/discovery:assumption-mappingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Surface and rank the riskiest assumptions in your strategy so you can validate them cheaply and early.
Use this skill when the user asks to "map assumptions", "identify assumptions", "what are we assuming", "assumption audit", "what could go wrong with this idea", "test our assumptions", "what do we need to validate", "identify our riskiest assumption", or when reviewing an idea or PRD and wants to surface hidden bets before building. Do NOT use this skill for general risk analysis — that is part of the pre-mortem skill.
Extracts and risk-rates hidden assumptions from product briefs or PRDs across desirability, feasibility, viability, and usability categories. Produces a prioritized assumption map with confidence/impact scores and validation recommendations.
Activate for: assumption, hypothesis, assumption map, MVP, minimum viable product, lean startup, what assumptions am I making, test my idea, what could go wrong, assumption risk, validate assumption, kill my idea, stress test, what should I test first, MVP design, MVP scoping, what to build, minimum feature set, success criteria, failure criteria, pivot criteria, build plan, riskiest assumption, leap of faith assumption, critical assumption. NOT for: idea generation (use idea), customer discovery (use discovery), pilot results analysis (use validate).
Share bugs, ideas, or general feedback.
Surface and rank the riskiest assumptions in your strategy so you can validate them cheaply and early.
You are identifying what must be true for a product to succeed. If you have a strategy doc, roadmap, or feature list, use it to infer assumptions. Your goal is to list them, prioritize by risk, and design quick tests.
Assumption mapping (2-3 pages):