assumption-mapping

Surface and rank risky product assumptions across four risk areas.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill assumption-mapping-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assumption-mapping
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/assumption-mapping
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill assumption-mapping-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assumption-mapping helps teams surface, classify, and prioritize risky beliefs embedded in a product idea or strategy, enabling early, risk-driven validation before a build begins.

Core Features & Use Cases

  • Identify and categorize assumptions across four risk areas: value risk, usability risk, business viability risk, and feasibility risk.
  • Score each assumption by importance to success and the evidence currently available, then prioritize the top 3–5 assumptions to test.
  • Design low-cost experiments and define explicit decision rules to validate or invalidate each assumption.
  • Produce a concise priority plan that guides product decisions and roadmap focus.

Quick Start

Restate the idea in concrete terms, surface the top 3–5 risky assumptions, and design low-cost experiments to validate each.

Frequently Asked Questions about assumption-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize risky assumptions for product validation?

Assumption mapping scores risky beliefs by importance to success and evidence available, prioritizing the top 3-5 assumptions to test with low-cost experiments and explicit decision rules.

What is assumption mapping and when do I need it?

Assumption mapping is a technique to surface, classify, and prioritize risky beliefs embedded in a product idea or strategy, enabling early, risk-driven validation before a build begins.

How do I categorize product risks before running experiments?

Categorize product risks across four specific areas: value risk, usability risk, business viability risk, and feasibility risk, then design low-cost experiments to validate each assumption.

What's the best way to design low-cost experiments for assumption validation?

Design low-cost experiments by defining explicit decision rules and clear validation criteria to validate or invalidate each prioritized assumption, guarding against unverifiable claims.

Does assumption mapping work for early-stage product ideas?

Assumption mapping is designed for early-stage validation, requiring only a concrete restatement of your idea to surface top risky assumptions and guide roadmap focus before development.

How many assumptions should I test in assumption mapping?

Assumption mapping focuses on testing the top 3-5 risky assumptions, producing an assumption table with prioritization, test proposals, and decision rules to guide product decisions.