πŸ§ͺ
AI EngineeringJavaScript

Define Hypothesis

by product-on-purpose

Define Hypothesis is an AI Engineering skill for Claude Code, published by product-on-purpose in pm-skills.

565 stars74 forkson product-on-purpose/pm-skillsAdded 2026/08/25+3% in starsRepository updated 2026/08/25
agent-skillsagentskillsai-skillsclaude-codeclaude-desktopcodexdesign-sprintfoundation-sprintopenskillsproduct-managementskill-familiestriple-diamond
Install in seconds
Install Define Hypothesis
Copy Define Hypothesis into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-hypothesis ~/.claude/skills/define-hypothesis

Requires Node.js. Downloads this skill only β€” not the rest of the repository β€” into your Claude Code skills folder.

Without Node.js

git clone https://github.com/product-on-purpose/pm-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/define-hypothesis/SKILL.md in product-on-purpose/pm-skills
Installs to
~/.claude/skills/define-hypothesis
Collection
One of 25 skills cataloged from this repository
Category
AI Engineering β€” 2451 skills

What Define Hypothesis does

Define Hypothesis turns an assumption into a falsifiable statement with a target user, success metrics, and a validation approach. Use it before designing an experiment or A/B test to align on what success looks like.

Define Hypothesis is cataloged under AI Engineering on DirSkills. Define Hypothesis comes from a repository tagged agent-skills, agentskills, ai-skills, claude-code and claude-desktop.

Documentation

README

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

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Define Hypothesis

  • What else does product-on-purpose publish alongside Define Hypothesis?

    Define Hypothesis is one of 25 skills that DirSkills catalogs from product-on-purpose/pm-skills, the repository it ships in. Its siblings there include Acceptance Criteria, Architecture Decision Record and Build Risk Review. Each one is a separate skill with its own page in this directory, installs the same way Define Hypothesis does, and is maintained by product-on-purpose in that same repository. The rest of the collection is listed on the product-on-purpose/pm-skills page.

  • How does Define Hypothesis compare to other AI Engineering skills?

    Define Hypothesis ranks #2013 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Define Hypothesis against them. Open each page to compare what they document and how they install.

More from product-on-purpose/pm-skills

Define Hypothesis is one of 25 skills cataloged on DirSkills from product-on-purpose/pm-skills.

See all 25 skills β†’
βœ…
6d ago

Acceptance Criteria

Acceptance Criteria generates testable Given/When/Then scenarios for a user story or feature slice. Use it when turning requirements into engineering handoff and QA sign-off criteria.
Quality
56574
πŸ“
6d ago

Architecture Decision Record

Architecture Decision Record documents a significant technical decision, its context, and consequences. Use it when choosing architecture, technology, or development patterns that future teams need to understand.
Writing
56574
🧭
6d ago

Build Risk Review

Build Risk Review names the single assumption most likely to make a product idea, feature request, or scope change fail, then returns a verdict and a no-code validation step. Use it before committing build effort or writing a PRD.
AI Engineering
56574
πŸ“Š
6d ago

Competitive Analysis

Competitive Analysis creates a structured comparison of 3-5 competitors across features, pricing, positioning, and strengths. Use it before entering a market, planning differentiation, or after losing deals.
Writing
56574
πŸ—ΊοΈ
6d ago

Customer Journey Map

Customer Journey Map maps a customer experience across stages, touchpoints, emotions, pain points, and moments of truth. Use it when synthesizing research into an end-to-end or phase-specific journey, and it refuses unsupported emotional or behavioral claims.
Data
56574
🧩
6d ago

Define Problem Statement

Define Problem Statement creates a structured problem framing document with user impact, business context, success criteria, constraints, and open questions. Use it when starting an initiative, realigning work, or briefing leadership.
Writing
56574