Assumption Mapper

Assumption Mapper Skill

Surface and prioritize the untested assumptions embedded in any product plan before development begins.

Required Inputs

Ask the user for these if not provided:

• Product brief, PRD, or concept description (even rough notes work)
• Stage (concept / discovery / pre-build / post-launch — affects which assumptions matter most)

Where this sits — the spine's entry point

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.

The loop

Four phases. Phase 3 is the skill; the rest feed it. Each ends on a completion criterion — don't advance until it's met.

1. Surface across all four lenses. Extract assumptions in Desirability (do users want it?), Feasibility (can we build it?), Viability (will the business sustain it?), Usability (can users actually use it?). The dangerous assumptions are the ones so obvious no one wrote them down. Done when: at least one assumption per lens, and re-reading the brief for the emptiest lens surfaces nothing new.
2. Rate on the two axes only. For each: load-bearing (1–5, does the plan collapse if it's false?) and confidence (1–5, how sure are we it's true?). Priority = load-bearing − confidence. Tag each fact's provenance ([data]/[hunch]). Done when: every assumption has both scores and a provenance tag, and the highest-priority one is genuinely the scariest — not the easiest to test.
3. Find and pressure the riskiest. The top-priority assumption (high-load-bearing × low-confidence) is the one that can sink the whole plan. Name the cheapest test that could disprove it before a line of code is written (see the disclosed cheap-tests reference for the menu). Done when: the single riskiest assumption is named, with a test that could run this week and a clear "what a fail looks like."
4. Hand off. Output the ranked map, and state explicitly which assumption /prd-template must treat as validated-or-open. An unresolved riskiest assumption becomes an Open Question in the PRD, not a silent bet. Done when: the downstream skill could start from this output without re-asking what the risky bet is.

Output Structure

Assumption Map: [Feature/Product Name]

Critical Assumptions (Impact 4+ and Confidence 2 or below)

[Flagged items with detailed validation recommendations]

Top 3 Assumptions to Validate First

[Detailed recommendations including specific research method, estimated effort, and what the result would change]

Example (Partial)

Input: "We're building a self-serve onboarding flow to reduce time-to-value for SMB customers."

Anti-Patterns

• Do not only surface desirability assumptions — feasibility and viability assumptions are equally likely to kill a product and are often overlooked
• Do not assign high confidence to an assumption just because it hasn't been challenged yet — absence of evidence is not evidence
• Do not recommend "user interviews" as the validation method for every assumption — some assumptions require quantitative data, competitive analysis, or technical spikes
• Do not list assumptions that cannot be tested — every assumption in the map must have a plausible validation method, or it should be flagged as unknowable and treated as a risk