skills.rest
muhammaddadu
muhammaddaduCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

epic-hypothesis

Frame epics as testable if/then hypotheses with experiments and validation measures.

1|1|Updated Jul 6, 2026
Search Tags:#product management#product validation#hypothesis testing#backlog#lean ux#epic hypothesis#discovery experiments
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill epic-hypothesis-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-hypothesis
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/1-exploration/epic-hypothesis
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill epic-hypothesis-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often commit to building large initiatives before validating demand, wasting engineering effort on features nobody wants. This Skill frames epics as falsifiable hypotheses with lightweight experiments and measurable success criteria before any build commitment. ## Core Features & Use Cases - If/Then Hypothesis Framing: Structure an epic around the action, target persona, and expected outcome using the Lean UX hypothesis format. - Tiny Acts of Discovery: Design fast, low-cost experiments such as prototypes, concierge tests, and landing page tests to validate assumptions. - Validation Measures: Define quantitative and qualitative success criteria with realistic timeframes so weak ideas can be killed early. - Use Case: Before adding a Google Calendar integration to the roadmap, draft a hypothesis, run a Figma prototype test with 10 trial users, and only proceed if activation metrics hit the defined threshold. ## Quick Start Use the epic-hypothesis skill to frame my proposed Slack notifications epic as a testable hypothesis with experiments and validation measures.

Frequently Asked Questions about epic-hypothesis

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

FAQPage Schema
How do I write an epic hypothesis for a product initiative?▼

Use the if/then structure: state the action or solution, the target persona, and the expected outcome. Then add lightweight discovery experiments and quantitative plus qualitative validation measures with a realistic timeframe.

What is the difference between an epic hypothesis and a feature spec?▼

An epic hypothesis states a falsifiable belief about user outcomes, not a committed feature. It defines experiments to test assumptions before building, while a feature spec describes what will be shipped.

What experiments validate an epic hypothesis before building?▼

Use lightweight tests such as clickable prototypes, concierge tests, landing page tests, Wizard of Oz tests, or A/B tests. Experiments should take days or weeks, cost little, and be capable of proving the hypothesis wrong.

When should I not use an epic hypothesis?▼

Skip it for well-validated features with proven demand, trivial changes, or cases where experiments are infeasible. In those situations go directly to user stories or delivery planning.

Why do epic hypotheses fail validation?▼

Common causes are vague outcomes, missing personas, experiments that are actually full builds, and subjective success measures. Fix these by specifying measurable metrics, defined personas, and falsifiable criteria within a 2-4 week window.

Related Skills

Explore More Product & Management Skills→
deanpetersdeanpeters
6.4k

problem-statement

Articulate user-centered problem narratives with an empathy-driven framing framework.

Community
Basic
akvoakvo
2

bmad-sm

Generate developer-ready user stories from PRD and architecture documents.

Official
Advanced
assimovtassimovt
54

feature-prioritization

Prioritize product features using RICE scoring and blocker versus enabler classification.

Community
Intermediate
jeffbalagosajeffbalagosa
1

openspec-explore

Guide reflective exploration of ideas and requirements without writing code.

Community
Basic