epic-hypothesis

Frame epics as testable hypotheses with target user, outcome, and validation method.

8|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/officebeats/beats-pm-kit --skill epic-hypothesis-officebeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-hypothesis
Source: https://github.com/officebeats/beats-pm-kit/tree/main/.agent/skills/epic-hypothesis
Command: npx skills add https://github.com/officebeats/beats-pm-kit --skill epic-hypothesis-officebeats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the uncertainty in product development by framing large initiatives (epics) as testable hypotheses, ensuring that development efforts are focused on validated outcomes rather than unproven assumptions.

Core Features & Use Cases

  • Hypothesis Formulation: Structures epics using an "If/Then" format, clearly stating the proposed action, target persona, and expected outcome.
  • Experiment Design: Guides the creation of "Tiny Acts of Discovery" – lightweight experiments to test core assumptions before full development.
  • Validation Metrics: Defines clear, measurable criteria to determine if the hypothesis is valid or invalidated.
  • Use Case: Before committing significant engineering resources to a new feature, use this Skill to define it as a hypothesis, design a quick prototype test, and set clear success metrics. If the test fails, the epic can be killed or pivoted, saving resources.

Quick Start

Use the epic-hypothesis skill to frame a new epic as a testable hypothesis.

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?

Framing epics as testable hypotheses involves using an if/then structure to articulate the proposed action, target persona, expected outcome, and validation method before committing to development.

What is a hypothesis-driven approach to product management for new features?

A hypothesis-driven approach addresses development uncertainty by defining major initiatives as testable assumptions with measurable validation metrics, ensuring efforts focus on validated outcomes rather than unproven ideas.

How do I design lightweight experiments to validate product assumptions?

You design lightweight experiments by creating Tiny Acts of Discovery that quickly test core assumptions through prototypes, establishing clear success criteria to determine if the hypothesis is valid or invalidated.

When should I use Lean UX hypothesis framing for product discovery?

Use Lean UX hypothesis framing before committing significant engineering resources to a new feature, during the discovery phase, or prior to roadmap and delivery planning to test major initiatives.

How do I define validation metrics for a product hypothesis?

Define validation metrics by establishing clear, measurable criteria during experiment design that determine whether the expected outcome is achieved or if the hypothesis is invalidated, allowing you to pivot or kill the epic.

What is the best way to structure a product hypothesis to prevent wasted engineering resources?

The best way to prevent wasted resources is structuring epics as testable hypotheses with defined target users and expected outcomes, running lightweight prototype tests, and relying on measurable validation metrics before full development.