Define Hypothesis
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Install
/plugin marketplace add product-on-purpose/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add product-on-purpose/pm-skills --skill define-hypothesisgit clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/define-hypothesis ~/.claude/skills/define-hypothesisPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Hypothesis A hypothesis is a testable prediction about how a change will affect user behavior or business outcomes. It transforms assumptions into explicit statements that can be validated or invalidated through experimentation. Well-formed hypotheses prevent teams from building features based on untested beliefs and create shared understanding of what success looks like. ## When to Use - After problem framing, before committing to a solution - When designing experiments or A/B tests - When team members have differing assumptions about user behavior - Before investing significant engineering resources in a feature - When pivoting direction and need to validate the new approach ## When NOT to Use - You are ready to design the actual A/B test (variants, sample size, duration) -> use `measure-experiment-design`; this skill frames what to test, not how - The problem itself is still unframed -> use `define-problem-statement` first - You want to organize many assumptions and ideas into a discovery structure -> use `define-opportunity-tree` - The team needs the full business-model picture, not one testable claim -> use `foundation-lean-canvas` ## Instructions When asked to create a hypothesis, follow these steps: 1. **State the Belief** Articulate what you believe will happen. Use the structured format: "We believe that [action/change] for [target user] will [expected outcome]." Be specific about the intervention - vague hypotheses can't be tested.
Details
- Skill name
define-hypothesis- Repository
- product-on-purpose/pm-skills
- Path
skills/define-hypothesis/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Define Hypothesis skill do?
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
How do I install the Define Hypothesis skill?
Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Define Hypothesis popular?
It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.
Related skills
<phase or Classification Skill Name>
819product-on-purpose/pm-skills
<single-line 20-100 word description; include trigger keywords and do not use folded YAML>
Define Jtbd Canvas
819product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Define Opportunity Tree
819product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.
Endpoint Definition Designer
2.1kaipoch/medical-research-skills
Designs primary, secondary, and exploratory endpoints for biomedical and clinical research protocols. Always use this skill when a user needs to translate study aims into operational endpoint definitions with event rules, assessment timing, composite logic, interpretability, and protocol-stage auditability. Focus on endpoint precision, feasibility, clinical meaning, ambiguity reduction, and implementation readiness rather than generic study design advice.
Define Problem Statement
819product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Za Retrenchment Package Check
1.6kmohitagw15856/pm-claude-skills
Check a retrenchment process and package for an employee in South Africa: whether consultation was done properly, the statutory minimum severance, notice pay, leave pay and other amounts, how the package is taxed, what an offer of alternative work means, and the deadlines for a dispute. Use when asked I got a section 189 letter, is my retrenchment package fair, calculate my severance pay, what am I owed if I am retrenched, or should I sign this retrenchment agreement. Produces a process check, a package table with working, a tax note, questions for the consultation, points to negotiate and the
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.