Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/assumption-mapper
Extract and risk-rate hidden assumptions in a product brief or PRD.
Passed 20 of 22 test cases with the skill, and 9 of 22 without it.
and 20 more in the full report
13 fixed7 passed either way0 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm about to start writing the PRD for an AI-powered automated meeting summarizer feature for our enterprise workspace tool, and we are currently at the pre-build stage. Before committing engineering resources, I need to surface all hidden risks and hypotheses across desirability, feasibility, viability, and usability. Please analyze our idea and give me a prioritized matrix detailing each assumption with category, confidence rating, impact score, priority calculation, and a validation method. Call out any high-risk critical bets that could derail the feature, and provide a top 3 priority list of tests to run this week, specifying research methods, estimated effort, and what decision each result will drive.
| Checked | Without skill | With skill |
|---|---|---|
| Calculates priority for each assumption strictly as Impact minus Confidence. | Missed | Passed |
| Tags each assumption with a provenance indicator of either [data] or [hunch]. | Missed | Passed |
| Flags assumptions with Impact rating of 4 or higher and Confidence rating of 2 or lower as Critical. | Missed | Passed |
The instructions your model reads when the skill loads.
Surface and prioritize the untested assumptions embedded in any product plan before development begins.
Ask the user for these if not provided:
This is the front of the product-decision spine: assumption-mapper → /prd-template
→ /rice-prioritisation → /roadmap-narrative. It takes a raw idea or brief and
hands the next skill one thing: the riskiest assumption, and whether it survived a
cheap test. Shared terms (assumption, load-bearing, confidence, provenance) are
defined once in docs/craft/product-decisions.md —
consult it rather than re-deriving them. Writing a PRD on top of an untested
load-bearing assumption is the failure this skill exists to prevent, so run it before
/prd-template, not after.
Four phases. Phase 3 is the skill; the rest feed it. Each ends on a completion criterion — don't advance until it's met.
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.