epic-hypothesis

Frame product management epics as testable hypotheses with if/then formats.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/archerli/skill-set --skill epic-hypothesis-archerli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-hypothesis
Source: https://github.com/archerli/skill-set/tree/main/%E4%BA%A7%E5%93%81%E7%BB%8F%E7%90%86/Product-Manager-Skills-main/skills/epic-hypothesis
Command: npx skills add https://github.com/archerli/skill-set --skill epic-hypothesis-archerli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The epic-hypothesis skill helps product managers address uncertainty in their roadmap by framing epics as testable hypotheses. It encourages explicit assumptions, lightweight experiments, and measurable success criteria.

Core Features & Use Cases

  • Epic Hypothesis Formatting: Provides a structured if/then format for defining epics as testable hypotheses.
  • Experiment Design: Outlines how to design and validate assumptions with experiments.
  • Outcome Tracking: Defines metrics to measure the validity of a hypothesis.
  • Use Case: When developing a new feature, create an epic hypothesis that outlines the action, target user, expected outcome, and validation method.

Quick Start

Frame your epic as a hypothesis using the format provided in the SKILL.md file.

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 management epic as a testable hypothesis?

To frame a product management epic as a testable hypothesis, use a structured if/then format to outline the target user, expected outcome, and validation method. This transforms epics into measurable experiments.

What is hypothesis-driven development in Lean UX?

Hypothesis-driven development in Lean UX is the practice of addressing roadmap uncertainty by defining explicit assumptions, designing lightweight experiments, and tracking measurable success criteria to validate product decisions.

How do I design experiments to validate product assumptions?

You design experiments to validate product assumptions by outlining specific validation methods within your epic hypothesis. This defines exactly how to measure the expected outcome and track the validity of your success metrics.

When should I use an epic hypothesis instead of a traditional feature roadmap?

You should use an epic hypothesis instead of a traditional roadmap when facing high uncertainty. It helps product managers explicitly define assumptions and use lightweight experiments to validate expected outcomes before full development.

Do I need prior Lean UX knowledge to use the epic-hypothesis format?

Yes, you need a foundational understanding of Lean UX principles and hypothesis-driven development. This knowledge is required to effectively define problem statements and structure your epics using the if/then format.

What metrics should I track to measure the validity of a hypothesis?

You should track metrics that directly measure the expected outcome defined in your epic hypothesis. These outcome metrics validate whether your target user behavior matches the assumptions outlined in your experiment design.