assumption-testing

Designs pre-registered assumption tests for desirability, viability, feasibility, and usability risks.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill assumption-testing-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: assumption-testing
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/assumption-testing
Command: npx skills add https://github.com/hero-engine/hero --skill assumption-testing-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product bets often rest on unchecked beliefs, and teams default to building an MVP to find out if they are right — an expensive, slow way to learn. This Skill gives agents a disciplined method to identify the riskiest assumption behind a bet and resolve it with a cheap, fast test before any build work begins. ## Core Features & Use Cases - Four Assumption Categories: Classify beliefs as desirability, viability, feasibility, or usability, then rank them by risk and confidence to pick what to test first. - Pre-Registration Discipline: A structured template forces a disconfirming signal and concrete pass/fail criteria to be written before the test runs, preventing confirmation-seeking. - Fast-Test Shapes: Choose from data pulls, 5-user interviews, concept tests, smoke tests, wizard-of-oz tests, and engineering spikes — all designed to resolve in days. - Use Case: A stakeholder proposes building an MVP to see if SMB users want self-serve data export. Instead, run a 4-day moderated concept test with 5 admins and pre-registered thresholds to decide whether to proceed, reframe, or kill the bet. ## Quick Start Ask the agent to design an assumption test for the riskiest belief behind your current product bet, with pre-registered pass/fail criteria that resolve within days.

Frequently Asked Questions about assumption-testing

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

FAQPage Schema
How do I test a product assumption before building an MVP?▼

Identify the assumption whose failure would most hurt the bet, then pick the cheapest test that can resolve it — a data pull, 5-user interview, concept test, smoke test, or wizard-of-oz test. Pre-register pass/fail criteria before running it.

What are the four types of product assumptions in discovery?▼

The four categories are desirability (do users want it), viability (does it work for the business), feasibility (can we build it within appetite), and usability (can users accomplish the job). Rank assumptions by risk and test the highest-risk, lowest-confidence one first.

Why is an MVP not a good assumption test?▼

An MVP is a delivery, not a test — it takes weeks, creates sunk cost, and returns results too entangled to isolate one assumption. A real test is cheaper than the thing it protects and resolves before you commit to building.

What is pre-registration in assumption testing?▼

Pre-registration means writing down the disconfirming signal and concrete pass/fail threshold before running the test. Deciding what the data means after seeing it is confirmation-seeking, not testing.

When should I use a smoke test versus a user interview?▼

Use a 5-user interview for fast desirability and usability signal through past-behavior questions. Use a smoke test (landing page or fake door) when you need measured real intent — signups or click-throughs — rather than stated intent.