ab-hypothesis-framing

Frame falsifiable A/B hypotheses with pre-registered metrics and decision rules.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill ab-hypothesis-framing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ab-hypothesis-framing
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/ab-hypothesis-framing/skills/ab-hypothesis-framing
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill ab-hypothesis-framing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frame a rigorous A/B test by creating falsifiable hypotheses, pre-registered metrics, and a risk-centric plan before execution, reducing bias and p-hacking.

Core Features & Use Cases

  • Falsifiable hypotheses with explicit mechanism
  • Pre-registered primary, secondary, and guardrail metrics
  • Minimum detectable effect (MDE) planning and sample-size estimation
  • Duration estimation and a pre-committed decision rule
  • Risk register and explicit peeking controls
  • Mermaid diagrams with optional PNG export for visualization

Quick Start

Frame a falsifiable A/B hypothesis with a concrete subject, proposed changes, and pre-registered metrics.

Frequently Asked Questions about ab-hypothesis-framing

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

FAQPage Schema
How do I frame a falsifiable A/B test hypothesis before running an experiment?▼

To frame a falsifiable A/B test hypothesis, define a concrete subject, propose specific changes, and pre-register primary, secondary, and guardrail metrics. This ensures your experiment design has an explicit mechanism and reduces bias before execution.

What is the best way to calculate sample size and minimum detectable effect for A/B testing?▼

The best way to calculate sample size and minimum detectable effect (MDE) is to plan them during experiment design. Estimating MDE and sample size upfront ensures your A/B test has sufficient statistical power to detect meaningful changes.

How can I prevent p-hacking and peeking during A/B experiment analysis?▼

Prevent p-hacking and peeking by establishing explicit peeking controls and a risk register before running experiments. Applying a pre-committed decision rule ensures your statistical analysis remains unbiased throughout the A/B test duration.

Can I plan A/B experiments with multiple variants and guardrail metrics?▼

Yes, you can plan A/B experiments with multiple variants. The framing process explicitly supports defining primary, secondary, and guardrail metrics alongside duration planning to ensure robust experiment design across all tested variations.

When do I need to define a pre-committed decision rule for experiment design?▼

You need to define a pre-committed decision rule for experiment design whenever running A/B tests. Establishing this rule before execution, alongside duration estimation and MDE planning, prevents biased outcomes and ensures rigorous statistical validation.