Frame epics as testable hypotheses with action, persona, outcome, and validation steps.
npx skills add https://github.com/ch-m-n/dotfile --skill epic-hypothesis-ch-m-n
Please help me install this Agent Skill. Skill: epic-hypothesis Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/epic-hypothesis Command: npx skills add https://github.com/ch-m-n/dotfile --skill epic-hypothesis-ch-m-n
Product teams often treat large initiatives as commitments without clarity on who benefits, what outcome is expected, or how success will be validated; this skill forces you to articulate epics as structured hypotheses so you can manage uncertainty before roadmap or delivery planning.
Use the epic hypothesis template to define an If/Then statement, experiments, and validation measures before committing to build.
High-intent search queries and answers about installing and using this skill.
A hypothesis-driven epic uses an If/Then structure to define the action, target persona, and expected outcome. This approach treats major initiatives as experiments, forcing teams to document validation measures and tiny acts of discovery before committing to delivery planning.
Tiny acts of discovery are lightweight experiments like prototypes, concierge tests, or landing pages used to test assumptions cheaply. They help validate epic hypotheses before investing significant engineering effort into full-scale delivery.
Use an epic hypothesis template during pre-roadmap stages to define an If/Then statement, outline lightweight experiments, and establish validation measures. This ensures every major initiative has measurable success criteria documented before moving to delivery planning.
Hypothesis-driven development replaces feature-focused commitments with outcome-focused experiments during discovery. Unlike traditional epics that dictate what to build, this approach defines target personas, expected outcomes, and validation steps to test assumptions cheaply before engineering investment.
The best way to manage uncertainty in product planning is to frame major initiatives as structured hypotheses with measurable success criteria. This requires documenting lightweight experiments and validation measures for each epic before moving to delivery planning.
tarunccetCreate testable product hypotheses with belief, user segment, metrics, and timeframe.
RebelHawk-TKFrame epics as If/Then hypotheses with discovery experiments and validation measures.
amo-tech-aiDesign, run, and analyze validation experiments for startup assumptions.
oldwinterGenerate an Uncertainty Planning Pack with hypothesis-driven plans and contingency triggers.
