experiment-design

Design hypothesis-driven A/B tests with statistical rigor and pre-committed plans.

54|4|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/assimovt/productskills --skill experiment-design-assimovt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-design
Source: https://github.com/assimovt/productskills/tree/main/skills/experiment-design
Command: npx skills add https://github.com/assimovt/productskills --skill experiment-design-assimovt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design rigorous, hypothesis-driven experiments and A/B tests, preventing common pitfalls that lead to inconclusive or misleading results.

Core Features & Use Cases

  • Hypothesis Formulation: Guides you in writing clear, measurable, and evidence-based hypotheses.
  • Experiment Setup: Defines primary and guardrail metrics, sample size calculations, and optimal duration.
  • Error Prevention: Highlights and helps avoid common mistakes like peeking at results, underpowered tests, and testing multiple changes at once.
  • Use Case: When launching a new feature, use this Skill to define a clear hypothesis, determine the necessary sample size for statistical significance, and set guardrail metrics to ensure no negative side effects.

Quick Start

Use the experiment-design skill to help me write a hypothesis for a new feature.

Frequently Asked Questions about experiment-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate sample size and duration for an A/B test to ensure statistical significance?

To calculate sample size and duration for A/B testing, you must define primary and guardrail metrics first. This ensures your experiment has adequate statistical power to reach significance and avoids underpowered tests that produce inconclusive or misleading results.

What is peeking in A/B testing and how do I prevent it from ruining my results?

Peeking in A/B testing is checking results before reaching the required sample size, which invalidates statistical significance. You can prevent this by establishing a pre-committed analysis plan that dictates exactly when and how to evaluate the experiment data.

How do I write a clear, measurable hypothesis for a new product feature?

Writing a clear hypothesis for a new product feature requires formulating an evidence-based, measurable prediction. It involves defining the expected change, selecting primary metrics to track, and setting guardrail metrics to catch any negative side effects during the A/B test.

Why does testing multiple variables simultaneously cause issues in experiment design?

Testing multiple variables simultaneously in experiment design causes issues by making it difficult to attribute observed metric changes to a specific variation. A pre-committed analysis plan helps structure tests to isolate variables and maintain statistical rigor.

What are guardrail metrics and when do I need them for hypothesis testing?

Guardrail metrics are secondary metrics used in hypothesis testing to ensure a new feature does not cause negative side effects. You need them during experiment setup alongside primary metrics to monitor overall system health and prevent unintended regressions.