epic-hypothesis — Claude Code skill: what it does, how to install
Frames initiative ideas as testable product hypotheses with target personas, expected outcomes, and discovery experiments. Useful before delivery planning.
npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a claude-codeWhat epic-hypothesis does
This skill turns an initiative or epic idea into an explicit if/then hypothesis. Instead of treating features as fixed delivery commitments, it frames them as measurable bets that can be proven wrong early.
The structure builds on Lean UX framing inspired by Tim Herbig. The workflow defines the solution, the target user, measurable business results, and small tests such as clickable prototypes, concierge tests, or landing pages. Sessions take 15 to 20 minutes.
Running this workflow on trivial tweaks or already validated features is a waste of time because its purpose is handling uncertainty.
What it helps with
- frame major product initiatives as testable hypotheses
- define measurable validation criteria before implementation
- design quick discovery experiments to test core assumptions
- clarify target personas and expected user outcomes
Example prompts for the agent
- Frame as an epic hypothesis: usage alerts so account admins prevent overages
- Help me turn bulk item deletion for power users into a testable hypothesis
How to install epic-hypothesis
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a claude-code2Manually: put the files in place
~/.claude/skills/epic-hypothesis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/epic-hypothesis/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a codex2Manually: put the files in place
.agents/skills/epic-hypothesis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a cursor2Manually: put the files in place
.cursor/skills/epic-hypothesis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills epic-hypothesis2Manually: put the files in place
.github/skills/epic-hypothesis/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/epic-hypothesisManually: put the files in place
.devin/skills/epic-hypothesis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about epic-hypothesis
How do I install epic-hypothesis in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill epic-hypothesis -a claude-code. The skill installs into your local configuration.
What does epic-hypothesis do?
It structures product initiatives into an if/then format covering target personas, expected results, and validation metrics. It turns feature backlogs into falsifiable bets.
When should this skill be skipped?
Skip it for minor adjustments or features where demand is already clear. It also adds little value when conducting early discovery experiments is impossible.