assumption-mapper
Assumption Mapper
Purpose
Expose hidden risks by identifying and ranking assumptions.
Categories
- Desirability (users want it)
- Feasibility (can we build it)
- Viability (business works)
Steps
- List assumptions in each category.
- Rate risk and uncertainty.
- Identify highest-risk assumption to test first.
Output
Key Assumptions
Highest-Risk Assumption
Validation Method
Decision Before Building
References
See worked example for a complete scenario.
More from pratikshadake/claude-product-management-skills
prd-critic
Evaluates PRD quality for clarity, testability, and build-readiness across problem clarity, scope, acceptance criteria, edge cases, and metrics. Use before sharing a PRD with engineering to catch gaps early.
20launch-readiness
Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.
18experiment-design
Designs fast, reliable validation experiments with hypothesis, method, success metric, and decision rules (Ship/Iterate/Kill). Use when you need to validate an assumption or test a product hypothesis before committing resources.
18value-vs-effort
Prioritizes features using structured scoring across user impact, revenue potential, strategic alignment, confidence, and engineering effort. Use when deciding which feature to build next or comparing competing priorities.
17roadmap-reality-checker
Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.
17problem-clarity
Evaluates whether a proposed idea addresses a genuine user problem worth solving. Use when assessing new feature ideas, startup concepts, or vague user complaints to determine if the pain justifies building a solution.
16