What problem does it solve? Teams often launch A/B tests with vague hypotheses, undefined metrics, or insufficient traffic, leading to invalid results and wasted effort. This Skill enforces a rigorous pre-launch workflow so every experiment is statistically sound before any code is written. ## Core Features & Use Cases - Hypothesis Lock Gate: Forces explicit confirmation of the hypothesis, target audience, primary metric, and Minimum Detectable Effect before design begins. - Metrics & Guardrails Framework: Defines one frozen primary metric, contextual secondary metrics, and guardrail metrics that block harmful wins. - Sample Size & Duration Planning: Requires baseline rate, significance level, and power to estimate sample size and test duration upfront. - Use Case: A product manager wants to test a new checkout button color. The Skill walks them through locking the hypothesis, verifying traffic can detect the expected effect, setting guardrails like page load time, and only then approving implementation. ## Quick Start Ask the assistant to help you design an A/B test for a specific product change and follow the guided gates through hypothesis, metrics, and execution readiness.