craft-experiment-design

Generate complete experiment plans with hypotheses, metrics, guardrails, and duration.

142|16|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/amplitude/builder-skills --skill craft-experiment-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: craft-experiment-design
Source: https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/craft-experiment-design
Command: npx skills add https://github.com/amplitude/builder-skills --skill craft-experiment-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Experiment Design helps you go from "we should test this" to a well-structured experiment design that your team and data scientists can review.

Core Features & Use Cases

  • Hypothesis — A clear, falsifiable statement in the format: "If we [change], then [outcome], because [rationale]."
  • Primary Metric — The single metric that determines success or failure.
  • Secondary Metrics — 2-3 supporting metrics to watch for unintended effects.
  • Guardrail Metrics — Metrics that must not degrade (e.g., error rates, latency, retention).
  • Audience & Allocation — Who should be in the test? What percentage split do you recommend?
  • Holdout Strategy — Should we maintain a holdout group after the test? Why or why not?
  • Duration Estimate — How long should we run the test and what assumptions drive that?
  • Risks & Considerations — What could go wrong or bias the results?

Quick Start

Draft a complete experiment plan with a falsifiable hypothesis, primary metric, secondary metrics, guardrails, audience allocation, a holdout decision, and an estimated duration.

Frequently Asked Questions about craft-experiment-design

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

FAQPage Schema
How do I design an A/B test with clear metrics and a falsifiable hypothesis?

To design an A/B test, formulate a falsifiable hypothesis stating the expected outcome and rationale, then define a single primary success metric, supporting secondary metrics, and guardrail metrics to prevent unintended degradation.

What guardrail metrics should I include in my experiment design?

Guardrail metrics in experiment design are critical health indicators that must not degrade, such as error rates, system latency, and user retention, ensuring your product changes do not cause unintended negative side effects.

How do I determine the right audience allocation and test duration for a product experiment?

Audience allocation and test duration are determined by identifying the target audience, recommending a percentage traffic split, and estimating the runtime based on statistical assumptions needed to reach a valid conclusion.

When should I use a holdout strategy in A/B testing?

A holdout strategy is used after an experiment concludes to maintain a control group, allowing you to measure the long-term impact and cumulative effect of shipping a feature compared to the baseline audience.

What is the best way to structure a product experiment plan for data science review?

A robust experiment plan includes a falsifiable hypothesis, primary and secondary metrics, guardrails, audience allocation, holdout decision, duration estimate, and risk considerations, providing a complete structure for team review.

What risks and biases should I consider when planning feature experiments?

When planning feature experiments, consider risks and factors that could bias results, such as incorrect audience allocation, insufficient test duration, or degradations in guardrail metrics like latency and error rates.