pm-experimentation-ab

Designs and reviews A/B tests with pre-registered hypotheses, sample-size calculations, and guardrail metrics.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-experimentation-ab-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-experimentation-ab
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/processes/experimentation-ab
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-experimentation-ab-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants routinely set up A/B tests that declare winners on tiny samples, stop at the first p < 0.05, optimize one metric with no guardrails, and end at "B won" with no learning loop. This Skill enforces statistical discipline so experiments produce trustworthy decisions instead of confident false conclusions. ## Core Features & Use Cases - Pre-registration discipline: Writes falsifiable if/then/because hypotheses with success and failure criteria plus pre-set iterate/pivot/persevere thresholds before the test runs. - Correct sizing and execution: Calculates sample size from baseline, MDE, and confidence level, derives duration, enforces a full business cycle, and prevents peeking and mid-test split changes. - Honest measurement and hand-off: Uses one primary metric plus guardrails, reads segments and long-term holdouts, documents results, and routes to metric-validity and assumption-rigor audits. - Use Case: Ask it to design an A/B test for a new checkout flow, and it will first check traffic sufficiency, compute the required sample size, set a 99% confidence threshold given the risk, define guardrail metrics like revenue and support volume, and pre-commit decision thresholds. ## Quick Start Ask the assistant to design an A/B test for your proposed change, including hypothesis, sample size, duration, primary and guardrail metrics, and decision thresholds.

Frequently Asked Questions about pm-experimentation-ab

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

FAQPage Schema
How do I design an A/B test with proper statistical rigor?▼

Start with a falsifiable if/then/because hypothesis, calculate sample size from your baseline metric and minimum detectable effect before running, and pre-set confidence level and decision thresholds. Run a full business cycle without peeking, and measure one primary metric plus guardrails.

How to calculate sample size and duration for an A/B test?▼

Compute users-per-variation from your baseline metric value, minimum detectable effect, and chosen confidence level (95% by default). Divide by daily traffic to derive duration, and always run at least one to two weeks to cover a full business cycle.

When should I not run an A/B test?▼

Avoid A/B testing when traffic is too low to reach a valid sample in reasonable time, when the idea is unvalidated, or when the question is why rather than which performs better. Route those cases to cheaper qualitative or low-fidelity assumption testing first.

What is the difference between A/B testing and multivariate testing?▼

A/B testing isolates one change cleanly and is the default choice. Multivariate testing finds interaction effects between elements but multiplies the sample required (four combinations need four times the traffic), so use it only on high-traffic surfaces.

Why is peeking at A/B test results a problem?▼

Stopping a test at the first p < 0.05 inflates false positives because significance fluctuates early in a run. Pre-set your confidence threshold and sample size, then let the test run to its planned duration before interpreting results.

What are guardrail metrics in product experiments?▼

Guardrail metrics are health indicators like revenue, churn, order value, support volume, or latency tracked alongside the primary metric. They catch cases where a winning variant quietly harms another part of the product or business.