What problem does it solve?
Epics are often treated as commitments rather than assumptions, causing teams to build large features without validating user value; this Skill helps teams make assumptions explicit, reduce wasted engineering effort, and manage risk by framing epics as falsifiable hypotheses.
Core Features & Use Cases
- If/Then Hypothesis Template: A concise structure that captures the action, target persona, and expected outcome to keep focus on outcomes over outputs.
- Experiment-first Guidance: Lists lightweight "tiny acts of discovery" (prototypes, concierge tests, landing pages, manual workflows) to validate assumptions before building.
- Validation Measures & Conversion: Defines measurable success criteria and timeframes, and provides steps to convert a validated hypothesis into user stories and roadmap items.
- Use Cases: Early-stage discovery, prioritizing backlog based on validated impact, stakeholder alignment by setting clear, testable expectations.
Quick Start
Draft an If/Then epic hypothesis for adding one-click calendar onboarding for trial users, list two quick experiments to test demand, and name measurable success criteria for a four-week evaluation.
