skills.rest
sicktastic
sicktasticCOMMUNITY
Explore all skills by this author →
Website𝕏@sicktasticGitHub

epic-hypothesis

Frame epics as If/Then hypotheses with experiments and validation measures.

Updated Apr 6, 2026
Search Tags:#validation#hypothesis#experimentation#epic#product-strategy#lean-ux
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill epic-hypothesis-sicktastic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-hypothesis
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/epic-hypothesis
Command: npx skills add https://github.com/sicktastic/skill-issue --skill epic-hypothesis-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents product teams from committing to large initiatives before validating the underlying assumptions by turning epics into experiment-ready hypotheses with measurable outcomes.

Core Features & Use Cases

  • If/Then Hypothesis Structure: Guides you to describe the action, target persona, and desired outcome in a falsifiable statement.
  • Tiny Acts of Discovery: Encourages lightweight experiments such as prototypes, concierge tests, or landing pages to prove or debunk the assumption.
  • Validation Measures: Forces clear timeframes and quantitative/qualitative criteria so you know when an epic is ready to be broken into stories or killed.
  • Use Case: Use this to prioritize unknown initiatives, align stakeholders on risk, and define success before roadmap planning.

Quick Start

Frame an epic hypothesis by writing the If/Then statement, listing tiny discovery experiments, and specifying validation metrics with a clear timeframe.

Frequently Asked Questions about epic-hypothesis

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

FAQPage Schema
How do I frame a product epic as a testable hypothesis?▼

Frame a product epic as a testable hypothesis by writing an If/Then statement that defines your action, target persona, and desired outcome. This makes underlying assumptions explicit rather than committing to unvalidated feature specs.

What is a lightweight experiment for validating product assumptions?▼

Lightweight experiments for validating product assumptions include tiny acts of discovery like building prototypes, running concierge tests, or launching landing pages to quickly prove or debunk the hypothesis.

How do you define validation measures for a product hypothesis?▼

Define validation measures by specifying clear timeframes alongside quantitative and qualitative criteria, establishing exact thresholds to determine when an epic is ready to be broken into stories or should be killed.

When should I use hypothesis-driven development for epics?▼

Use hypothesis-driven development when defining early epics across product discovery, prioritization, and stakeholder communication, ensuring teams remain aligned on measurable outcomes before roadmap planning and delivery.

How do I align stakeholders on product risk before roadmap planning?▼

Align stakeholders on product risk by framing unknown initiatives as measurable bets with explicit assumptions and validation timeframes, shifting focus from feature delivery to proving underlying business outcomes.

Related Skills

Explore More Product & Management Skills→
sinositatosinositato

prd-discover

Gather problem, user, scope, and success criteria into a markdown context file.

Community
Intermediate
EchoNoReturnEchoNoReturn

epic-hypothesis

Frame epics as If/Then hypotheses with tiny experiments and validation measures.

Community
Advanced
MiDouTechMiDouTech

roadmap-planning

Convert strategic inputs into testable epics with success metrics and quarterly sequencing.

Official
Advanced
tabooestabooes
1

epic-hypothesis

Frame epics as If/Then hypotheses with validation measures.

Community
Advanced