assumption-mapper
Assumption Mapper extracts untested assumptions from product briefs and PRDs across four categories (desirability, feasibility, viability, usability), scores each by confidence and impact, and prioritizes validation efforts. Use this skill when reviewing product plans for hidden risks, auditing requirements documents, or validating strategic decisions before development begins.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/assumption-mapper && cp -r /tmp/assumption-mapper/plugins/pm-discovery/skills/assumption-mapper ~/.claude/skills/assumption-mapperSKILL.md
# 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) ## Process 1. Read the provided brief, PRD, or concept description 2. Extract assumptions across four categories: - **Desirability** (do users want this?) - **Feasibility** (can we build it?) - **Viability** (will it sustain the business?) - **Usability** (can users actually use it?) 3. Score each assumption: - Confidence (1-5): How sure are we this is true? - Impact (1-5): How badly does the plan fail if this assumption is wrong? - Priority = Impact − Confidence (higher = test first) 4. **Validate completeness** — Ensure at least one assumption per category. If a category is empty, re-read the brief looking specifically for that type. 5. Output a ranked list with recommended validation methods ## Output Structure ### Assumption Map: [Feature/Product Name] | Assumption | Category | Confidence | Impact | Priority | Validation Method | |------------|----------|------------|--------|----------|-------------------| | [assumption] | [type] | [1-5] | [1-5] | [score] | [method] | #### 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."* | Assumption | Category | Confidence | Impact | Priority | Validation Method | |------------|----------|------------|--------|----------|-------------------| | SMB users can complete onboarding without human help | Usability | 2 | 5 | 3 | Unmoderated usability test (n=8) | | Faster onboarding correlates with higher retention | Viability | 3 | 4 | 1 | Cohort analysis of current onboarding times vs. 90-day retention | | The current onboarding is the primary reason for slow time-to-value | Desirability | 2 | 4 | 2 | User interviews with recent churned SMB accounts | ## 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 ## Quality Checks - [ ] At least one assumption per category (Desirability, Feasibility, Viability, Usability) - [ ] All Impact 4+ / Confidence 2− assumptions flagged as CRITICAL - [ ] Each validation method is specific (not just "do research" — name the method and sample size) - [ ] Priority scores are consistent (Impact − Confidence, higher = more urgent)
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.