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.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/ab-test-design-brief/SKILL.md
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.4---567# A/B Test Design Brief89Use this skill to turn a product change into a decision-ready A/B test brief.10It focuses on experiment anatomy: hypothesis, metrics, baselines, variants,11eligibility, randomization, confidence, and launch criteria.1213## Source Traceability1415Primary source: Practical A/B Testing by Leemay Nassery. Guidance is16transformed and paraphrased from chapter 2, especially "Creating a Clear17Hypothesis" through "Summarizing the For You A/B Test" in the working text18analysis at lines 1203-1942. Related motivation and variant examples come from19chapter 1 lines 394-718.2021## Related Advanced Skills2223- `experiment-sensitivity-optimization`: use when the brief is blocked by MDE,24 sample size, noisy metrics, CUPED, capping, or too many variants.25- `experiment-verification-monitoring`: use when the brief needs prelaunch QA,26 canaries, exposure validation, or active experiment health checks.27- `long-term-impact-evaluation`: use when the brief needs delayed or sustained28 impact measurement beyond the initial test window.2930## Reference Routing3132| Need | Read |33|------|------|34| Concepts and terminology | `references/core/knowledge.md` |35| Design rules and readiness checks | `references/core/rules.md` |36| Brief examples and anti-examples | `references/core/examples.md` |37| Step-by-step brief creation | `workflows/create-ab-test-brief.md` |3839## Workflow40411. State the product decision the test must inform.422. Write a hypothesis with observation, predicted change, audience, and metrics.433. Choose one primary success metric plus guardrail metrics.444. Establish the baseline or explain why a proxy metric is being used.455. Define eligibility, exposure, test variant, and control variant.466. Choose the randomization unit that preserves a coherent user experience.477. Record confidence requirements, sample-size assumptions, and launch criteria.4849## Output Format5051```markdown52# A/B Test Brief5354## Decision55[What decision this test will support.]5657## Hypothesis58Because [observation], we believe [change] will cause [outcome] for [audience].59We will know this is true when [primary metric] changes without harming [guardrails].6061## Metrics62| Metric | Role | Baseline | Target or Concern | Data Source |63|--------|------|----------|-------------------|-------------|6465## Variants and Eligibility66- Population:67- Eligibility criteria:68- Exposure event:69- Control:70- Test:71- Randomization unit:7273## Confidence Plan74- Minimum detectable effect:75- Sample size or duration:76- Risks to validity:7778## Launch Criteria79- Ship if:80- Do not ship if:81- Investigate if:82```8384## Quality Bar8586- Do not accept a vague "see what happens" experiment.87- Do not let proxy metrics hide missing instrumentation; name the compromise.88- Do not generalize beyond the population that was eligible and exposed.89- Keep variants interpretable: if many things change, the learning becomes weak.9091---9293**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/ab-test-design-brief/SKILL.md`