measure-experiment-design
Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis. Use when planning an experiment to validate a product change or test an assumption you have already framed. To articulate the hypothesis itself first, use define-hypothesis.
npx skills add product-on-purpose/pm-skills --skill measure-experiment-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Experiment Design An experiment design document defines all parameters needed to run a rigorous A/B test or controlled experiment. It ensures the team aligns on what you're testing, how you'll measure success, and how long to run the test before drawing conclusions. Good experiment design prevents common pitfalls: underpowered tests, unclear success criteria, and decisions based on noise rather than signal. ## When to Use - Before launching an A/B test to validate a product change - When testing a hypothesis that requires quantitative validation - After solution design to validate assumptions before full rollout - When stakeholders want data-driven evidence for a decision - To establish a culture of experimentation and learning ## When NOT to Use - The hypothesis itself is not yet articulated -> use `define-hypothesis` first; this skill designs the test for a claim you already have - You are analyzing a completed experiment -> use `measure-experiment-results` - You need the event tracking that will measure the experiment -> use `measure-instrumentation-spec` - You are gathering opinions rather than
- When to Use
- When NOT to Use
- Instructions
- Output Format
- Quality Checklist
- Examples
What does the measure-experiment-design skill do?
Designs an A/B test or experiment with variants, success metrics, sample size, and duration for an existing hypothesis. Use when planning an experiment to validate a product change or test an assumption you have already framed. To articulate the hypothesis itself first, use define-hypothesis.
How do I install it?
Run `npx skills add product-on-purpose/pm-skills --skill measure-experiment-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.