This frames product epics as falsifiable hypotheses instead of feature commitments. You write an if/then statement (if we build X for persona Y, then outcome Z), design cheap experiments to test it before building anything real, and set measurable success criteria with a timeframe. The structure forces you to name your assumptions explicitly and gives you permission to kill ideas that don't validate. Use it when you're exploring new features and want to avoid building the wrong thing. Skip it for proven features where you already have demand signals. The "tiny acts of discovery" framing is particularly useful for getting stakeholders comfortable with running lightweight tests instead of jumping straight to engineering work.
npx -y skills add deanpeters/product-manager-skills --skill epic-hypothesis --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills