experiment-design

Guide product experiment design, execution, and analysis for A/B testing.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/pe-menezes/pmflow --skill experiment-design-pe-menezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-design
Source: https://github.com/pe-menezes/pmflow/tree/main/skills/experiment-design
Command: npx skills add https://github.com/pe-menezes/pmflow --skill experiment-design-pe-menezes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product managers design, execute, and interpret experiments to make data-driven product decisions, ensuring rigorous methodology from hypothesis to iteration.

Core Features & Use Cases

  • Experiment Design: Define test parameters, calculate sample sizes, and plan user assignment.
  • Launch & Monitoring: Guide through safe launch procedures, monitoring, and early stopping criteria.
  • Analysis & Iteration: Facilitate calling tests, segmenting results, and planning next steps based on learnings.
  • Use Case: You have a new feature idea and need to A/B test its impact on user conversion. This Skill will guide you through defining the hypothesis, calculating the necessary sample size, planning the rollout, and analyzing the results to determine if the feature should be implemented.

Quick Start

Use the experiment-design skill to design an experiment for a new signup flow.

Frequently Asked Questions about experiment-design

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

FAQPage Schema
How do I design an A/B test for a new product feature?

A/B testing requires defining test parameters, calculating sample sizes, and planning user assignment to ensure rigorous methodology. This process validates product hypotheses and enables data-driven decisions before full implementation.

What is the best way to calculate sample size for product experiments?

Calculating sample size for product experiments requires defining statistical parameters and user assignment strategies. Accurate calculation ensures your A/B test has sufficient power to detect meaningful changes in user conversion metrics.

How do I monitor A/B tests and decide when to stop them early?

Monitoring A/B tests involves tracking metrics against pre-defined early stopping criteria during launch. This prevents prolonged exposure to underperforming variants and protects user experience while maintaining statistical rigor.

Can I segment A/B test results to understand different user behaviors?

Segmenting A/B test results involves analyzing how different user cohorts respond to the experiment. This segmentation identifies varying impacts across user groups, informing targeted iteration plans and subsequent product strategy decisions.

When should I not use A/B testing for product analytics?

A/B testing may not be suitable when sample sizes are insufficient for statistical significance or when user assignment strategies become overly complex. In these cases, alternative product analytics methods might provide more reliable insights.