Convert PMContext product risks into a prioritized eight-category assumption map.
npx skills add https://github.com/Wcof/PMSkill --skill pm-assumption
Please help me install this Agent Skill. Skill: pm-assumption Source: https://github.com/Wcof/PMSkill/tree/main/skills/discovery/pm-assumption Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-assumption
This Skill helps product teams uncover the hidden assumptions that could cause a product idea to fail before time and budget are wasted. It turns an implicit PMContext into an explicit risk map across eight categories, so teams can see what must be true, how confident they are, and what should be tested first.
Ask the AI to use pm-assumption on the current PMContext to identify all eight risk categories, rank the top assumptions, and propose the cheapest test for each top risk.
High-intent search queries and answers about installing and using this skill.
Assumption mapping identifies hidden product risks across categories like Value, Usability, and Viability. It converts implicit product context into a prioritized risk register with confidence scoring and impact-likelihood rankings.
Prioritize product assumptions by scoring their impact and likelihood of being wrong. Apply confidence scoring to each risk category, then rank them to highlight the highest-risk unknowns requiring immediate validation testing.
Map product risk assumptions by evaluating eight categories: Value, Usability, Viability, Feasibility, Ethics, GTM, Strategy, and Team. This structured risk review highlights missing categories needing confirmation before PRD preparation.
Plan cheap validation tests by building a staged testing ladder for your top ranked assumptions. Define low-cost validation steps for each high-impact risk to move rapidly from team discussion to evidence.
Assumption mapping requires a complete product context to generate a full risk register. If context is incomplete, the mapping highlights missing risk categories with a placeholder tag for later confirmation.
Avoid assumption mapping when you lack any product context, as it requires existing PMContext data to identify risks. It is also unnecessary for minor updates lacking strategy, viability, or feasibility risks.
WcofDefine a north star metric and input metrics framework from PMContext requirements.
jshsakuraSurface and rank risky product assumptions across four risk areas.
Lev-itIdentify and rank critical assumptions in strategy and product documents.
officebeatsPrioritize product assumptions using an Impact × Risk matrix and suggest validation experiments.
