Hypothesis

Write testable product hypotheses with clear success metrics, baselines, targets, and timeframes. Produces a structured hypothesis statement, supporting evidence, a validation plan with method and sample size, and a decision framework for what to do if validated or invalidated. Use when validating product assumptions, before running experiments, when proposing new features, or when shifting from opinion-based to evidence-based decision making.

9 stars 2 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tarunccet/pm-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tarunccet/pm-skills --skill hypothesis
Manual install
git clone --depth 1 https://github.com/tarunccet/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-discovery/skills/hypothesis ~/.claude/skills/hypothesis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Hypothesis: Testable Beliefs with Success Metrics

## Purpose

You are an experienced product manager helping a team write a testable hypothesis for **$ARGUMENTS**. A well-formed hypothesis turns opinions into experiments — it forces clarity about what we believe, why we believe it, and exactly how we'll know if we're right or wrong.

## Domain Context

Hypotheses sit between problem definition and experimentation in the discovery workflow. In a lean/agile product organization, every feature bet should start as a hypothesis — a falsifiable statement that can be validated cheaply before the team commits significant engineering effort. Teresa Torres's Continuous Discovery framework and Eric Ries's Lean Startup both depend on disciplined hypothesis writing.

A strong hypothesis follows this structure:

> "We believe that **[action/change]** for **[user segment]** will result in **[expected outcome]**, as measured by **[metric]** changing from **[baseline]** to **[target]** within **[timeframe]**."

This skill pairs well with **brainstorm-experiments-existing** and **brainstorm-experiments-new** for designing the actual experiment, and with **problem-statement** for grounding the hypothesis in a validated problem.

### What You'll Need

| Input | Required? | Example |
|-------|-----------|---------|
| Feature idea, assumption, or belief to test | ✅ Required | "Adding onboarding tooltips will improve activation" |
Read the full skill on GitHub

Details

Skill name
hypothesis
Path
pm-product-discovery/skills/hypothesis/SKILL.md
License
MIT
Repo updated
13 November 2026

FAQ

What does the Hypothesis skill do?

Write testable product hypotheses with clear success metrics, baselines, targets, and timeframes. Produces a structured hypothesis statement, supporting evidence, a validation plan with method and sample size, and a decision framework for what to do if validated or invalidated. Use when validating product assumptions, before running experiments, when proposing new features, or when shifting from opinion-based to evidence-based decision making.

How do I install the Hypothesis skill?

Claude Code plugin: /plugin marketplace add tarunccet/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Hypothesis popular?

It lives in tarunccet/pm-skills, which has 9 GitHub stars and 2 forks.

Related skills

Ab Test Analysis

9

tarunccet/pm-skills

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

Testing & QA

Adr

9

tarunccet/pm-skills

Document architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any decision that will be hard to reverse.

Software Development

AI Build Buy Partner

9

tarunccet/pm-skills

Evaluate AI capability sourcing options across build, buy, fine-tune, and partner archetypes using a structured decision matrix. Use when deciding whether to build a custom model, use an LLM API, fine-tune a base model, or partner with an AI vendor.

AI, LLMs & Agents

Job Stories

9

tarunccet/pm-skills

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

Writing & Content

Create Prd

9

tarunccet/pm-skills

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Writing & Content

Rent Analysis

5

analyticsariel/tech-in-real-estate

Compare county rents in any US state using Zillow's ZORI file. Use when asked how rents in a county are moving, how two counties compare, or whether to raise or hold rent. Runs rent_report.py, then explains what the index measures and what it can't tell you.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.