pm-abtest

Plan A/B tests with hypothesis, metrics, sample size, and duration.

46|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-abtest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-abtest
Source: https://github.com/konglong87/superPM/tree/main/skills/03-growth-iteration/pm-abtest
Command: npx skills add https://github.com/konglong87/superPM --skill pm-abtest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you validate product or feature changes by turning vague optimization ideas into a statistically grounded A/B test plan, including hypothesis, metrics, sample size, runtime, and decision rules.

Core Features & Use Cases

  • Hypothesis & Metrics Setup: Define test hypotheses plus primary/secondary/guardrail metrics to ensure you measure the right outcome without harming user experience.
  • Sample Size & Test Duration Planning: Estimate required sample size and propose a realistic test period based on provided baseline parameters and traffic assumptions.
  • Data Collection & Analysis Framework: Specify event/metric collection guidance and an analysis workflow (cleaning, descriptive stats, hypothesis testing, effect size, segmentation).
  • Auto-generate Test Plan Docs: Write a structured A/B test方案 into docs/03-增长迭代/A-B测试/ for execution and later analysis.

Quick Start

Ask the AI to run an A/B test planning session for your optimization idea, and it will guide you to define the hypothesis, choose metrics, estimate sample size and duration, and generate the test plan document.

Frequently Asked Questions about pm-abtest

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

FAQPage Schema
How do I design an A/B test to validate a product change?

To design an A/B test, you must define a clear hypothesis, establish primary and guardrail metrics, estimate the required sample size, and set test duration rules to validate the product change. This ensures causal measurement without harming user experience.

What metrics do I need for A/B test experiment design?

A/B test experiment design requires primary metrics to measure the target improvement, secondary metrics for broader context, and guardrail metrics to ensure the product change does not negatively impact existing user experience.

How do I estimate sample size and test duration for data analysis?

Sample size and test duration are estimated using baseline parameters and traffic assumptions. Calculating these ensures your A/B test collects sufficient data to achieve statistical significance for reliable product optimization decisions.

Can I generate a structured A/B test plan document automatically?

Yes, a structured A/B test plan document can be generated automatically. It writes the complete experimental design, including hypotheses, metrics, and runtime rules, into a designated directory for execution and later data analysis.

What is the data collection and analysis framework for A/B testing?

The A/B testing analysis framework specifies event collection guidance and a workflow covering data cleaning, descriptive statistics, hypothesis testing, effect size calculation, and segmentation to interpret experiment results accurately.

When should I use guardrail metrics in product optimization experiments?

Guardrail metrics should be used in every product optimization experiment to monitor predefined thresholds. They prevent negative impacts on user experience or core business metrics when testing new feature changes.