A/B Test Design Brief
Use this skill to turn a product change into a decision-ready A/B test brief.
It focuses on experiment anatomy: hypothesis, metrics, baselines, variants,
eligibility, randomization, confidence, and launch criteria.
Source Traceability
Primary source: Practical A/B Testing by Leemay Nassery. Guidance is
transformed and paraphrased from chapter 2, especially "Creating a Clear
Hypothesis" through "Summarizing the For You A/B Test" in the working text
analysis at lines 1203-1942. Related motivation and variant examples come from
chapter 1 lines 394-718.
Related Advanced Skills
experiment-sensitivity-optimization: use when the brief is blocked by MDE,
sample size, noisy metrics, CUPED, capping, or too many variants.
experiment-verification-monitoring: use when the brief needs prelaunch QA,
canaries, exposure validation, or active experiment health checks.
long-term-impact-evaluation: use when the brief needs delayed or sustained
impact measurement beyond the initial test window.
Reference Routing
| Need |
Read |
| Concepts and terminology |
references/core/knowledge.md |
| Design rules and readiness checks |
references/core/rules.md |
| Brief examples and anti-examples |
references/core/examples.md |
| Step-by-step brief creation |
workflows/create-ab-test-brief.md |
Workflow
- State the product decision the test must inform.
- Write a hypothesis with observation, predicted change, audience, and metrics.
- Choose one primary success metric plus guardrail metrics.
- Establish the baseline or explain why a proxy metric is being used.
- Define eligibility, exposure, test variant, and control variant.
- Choose the randomization unit that preserves a coherent user experience.
- Record confidence requirements, sample-size assumptions, and launch criteria.
Output Format
# A/B Test Brief
## Decision
[What decision this test will support.]
## Hypothesis
Because [observation], we believe [change] will cause [outcome] for [audience].
We will know this is true when [primary metric] changes without harming [guardrails].
## Metrics
| Metric | Role | Baseline | Target or Concern | Data Source |
|--------|------|----------|-------------------|-------------|
## Variants and Eligibility
- Population:
- Eligibility criteria:
- Exposure event:
- Control:
- Test:
- Randomization unit:
## Confidence Plan
- Minimum detectable effect:
- Sample size or duration:
- Risks to validity:
## Launch Criteria
- Ship if:
- Do not ship if:
- Investigate if:
Quality Bar
- Do not accept a vague "see what happens" experiment.
- Do not let proxy metrics hide missing instrumentation; name the compromise.
- Do not generalize beyond the population that was eligible and exposed.
- Keep variants interpretable: if many things change, the learning becomes weak.
1---2name: ab-test-design-brief3description: Build product A/B test briefs with hypotheses, success metrics, guardrails, baselines, proxy metrics, eligibility, variants, randomization, confidence, and launch criteria. Use when planning an A/B test from a product idea, writing an experiment spec, defining test/control variants, choosing metrics, or checking whether an experiment is ready to run.4license: MIT5compatibility: Codex, Claude Code, and other Agent Skills-compatible clients.6metadata:7 version: "0.1.0"8 displayName: A/B Test Design Brief9 category: Product Management10 tags: practical-ab-testing,ab-testing,experimentation,product-analytics,metrics11---1213# A/B Test Design Brief1415Use this skill to turn a product change into a decision-ready A/B test brief.16It focuses on experiment anatomy: hypothesis, metrics, baselines, variants,17eligibility, randomization, confidence, and launch criteria.1819## Source Traceability2021Primary source: Practical A/B Testing by Leemay Nassery. Guidance is22transformed and paraphrased from chapter 2, especially "Creating a Clear23Hypothesis" through "Summarizing the For You A/B Test" in the working text24analysis at lines 1203-1942. Related motivation and variant examples come from25chapter 1 lines 394-718.2627## Related Advanced Skills2829- `experiment-sensitivity-optimization`: use when the brief is blocked by MDE,30 sample size, noisy metrics, CUPED, capping, or too many variants.31- `experiment-verification-monitoring`: use when the brief needs prelaunch QA,32 canaries, exposure validation, or active experiment health checks.33- `long-term-impact-evaluation`: use when the brief needs delayed or sustained34 impact measurement beyond the initial test window.3536## Reference Routing3738| Need | Read |39|------|------|40| Concepts and terminology | `references/core/knowledge.md` |41| Design rules and readiness checks | `references/core/rules.md` |42| Brief examples and anti-examples | `references/core/examples.md` |43| Step-by-step brief creation | `workflows/create-ab-test-brief.md` |4445## Workflow46471. State the product decision the test must inform.482. Write a hypothesis with observation, predicted change, audience, and metrics.493. Choose one primary success metric plus guardrail metrics.504. Establish the baseline or explain why a proxy metric is being used.515. Define eligibility, exposure, test variant, and control variant.526. Choose the randomization unit that preserves a coherent user experience.537. Record confidence requirements, sample-size assumptions, and launch criteria.5455## Output Format5657```markdown58# A/B Test Brief5960## Decision61[What decision this test will support.]6263## Hypothesis64Because [observation], we believe [change] will cause [outcome] for [audience].65We will know this is true when [primary metric] changes without harming [guardrails].6667## Metrics68| Metric | Role | Baseline | Target or Concern | Data Source |69|--------|------|----------|-------------------|-------------|7071## Variants and Eligibility72- Population:73- Eligibility criteria:74- Exposure event:75- Control:76- Test:77- Randomization unit:7879## Confidence Plan80- Minimum detectable effect:81- Sample size or duration:82- Risks to validity:8384## Launch Criteria85- Ship if:86- Do not ship if:87- Investigate if:88```8990## Quality Bar9192- Do not accept a vague "see what happens" experiment.93- Do not let proxy metrics hide missing instrumentation; name the compromise.94- Do not generalize beyond the population that was eligible and exposed.95- Keep variants interpretable: if many things change, the learning becomes weak.