epic-hypothesis
by deanpetersepic-hypothesis helps you frame an epic as a testable hypothesis with a target user, expected outcome, experiments, and validation. Use the epic-hypothesis skill to turn broad initiatives into clearer product decisions before roadmap, discovery, or delivery work.
This skill scores 78/100, which means it is a solid directory listing candidate with enough real workflow value to help agents frame epics as testable hypotheses instead of vague feature requests. Users should find it worthwhile to install if they work on product discovery or roadmap planning, though they should expect a mostly document-based skill rather than one backed by scripts or automated checks.
- Clear, explicit trigger: use when defining a major initiative before roadmap, discovery, or delivery planning.
- Strong operational structure: if/then hypothesis, tiny acts of discovery, and validation measures are spelled out in the skill and template.
- Good install decision value: includes a worked example and a bad-example contrast that reduce guesswork for agents.
- No scripts, rules, or support files, so execution depends entirely on reading and following the markdown guidance.
- The skill is narrowly scoped to epic hypothesis framing; it helps with discovery language, not broader product planning workflows.
Overview of epic-hypothesis skill
What epic-hypothesis does
The epic-hypothesis skill helps you turn a broad epic into a testable hypothesis instead of a vague delivery statement. It is useful when you need to define an initiative before roadmap commitment, discovery, or build work, and you want the epic to state who it helps, what changes, and how you will know it worked.
Who it is best for
This epic-hypothesis skill is a good fit for product managers, technical writers, design leads, and cross-functional teams that need clearer initiative framing. It is especially useful for epic-hypothesis for Technical Writing because it gives writers a concrete structure for translating messy business intent into a readable decision artifact.
What makes it different
The main value is not the wording template itself, but the discipline it creates: a target persona, an outcome, and a validation plan. That makes epic-hypothesis more decision-useful than a generic prompt, because it forces assumptions and success criteria into the open before anyone starts drafting requirements.
How to Use epic-hypothesis skill
Install and open the source files
Use the repo path deanpeters/Product-Manager-Skills and install the epic-hypothesis skill through your skill manager, or read it directly from skills/epic-hypothesis. Start with SKILL.md, then open template.md and examples/sample.md to see the exact hypothesis pattern and what “good” versus “bad” looks like.
Give the skill a real epic, not a theme
For best epic-hypothesis usage, pass in a rough initiative with enough context to identify the user, the problem, and the intended change. Strong inputs mention the persona, business goal, constraint, and what success looks like.
Example prompt shape:
Use epic-hypothesis to frame an epic for trial users who churn after onboarding. The initiative is a calendar integration. We need a hypothesis, 2-3 discovery experiments, and measurable validation criteria.
Weak input:
Write an epic hypothesis for dashboards.
Follow the repository workflow
The epic-hypothesis guide is built around three parts: If/Then Hypothesis, Tiny Acts of Discovery Experiments, and Validation Measures. Use that sequence when drafting. If your team already has product language, translate it into the template rather than rewriting it from scratch; the skill is strongest when it turns existing thinking into testable form.
Tips that improve output quality
Name the audience precisely, avoid solution-free wording, and include a time-bound validation window. If you do not know the metric yet, ask the skill to propose one, but give it the business context so the metric is relevant. For Technical Writing workflows, ask for wording that is concise enough to live in planning docs and review notes, not just in strategy decks.
epic-hypothesis skill FAQ
Is epic-hypothesis only for product managers?
No. The epic-hypothesis skill is useful anywhere a team needs to reduce ambiguity before committing to work. Technical writers can use it to frame documentation-related initiatives, and delivery teams can use it to align on outcomes before implementation.
How is this different from a normal prompt?
A normal prompt may produce a polished paragraph, but epic-hypothesis gives you a reusable decision structure. The skill is better when you want traceable assumptions, explicit experiments, and measurable validation rather than a one-off brainstorm.
When should I not use it?
Do not use epic-hypothesis when the work is already well-understood, scope is fixed, or you only need a simple status update. It is most valuable when uncertainty is high and you need to decide whether an epic is worth pursuing.
Is it beginner-friendly?
Yes, if you can describe the initiative in plain language. The template is straightforward, but the quality depends on how clearly you define the target user, outcome, and validation method. If those are fuzzy, the first draft will be fuzzy too.
How to Improve epic-hypothesis skill
Start with sharper inputs
The fastest way to improve epic-hypothesis results is to provide a specific persona, a concrete pain point, and the smallest measurable outcome that would prove value. For example, “new admins who abandon setup after step 2” is far better than “users who struggle.”
Watch for common failure modes
The most common mistake is writing a disguised feature spec instead of a hypothesis. Another is using validation measures that are too broad, such as “users like it.” Good epic-hypothesis output should make it clear what evidence would change your mind.
Iterate after the first draft
After the first pass, refine the hypothesis by tightening the audience, replacing generic outcomes with business-relevant ones, and lowering the experiment cost. If the output feels abstract, ask the skill to rewrite it for epic-hypothesis for Technical Writing or to make the validation criteria more specific and observable.