# Ab Test Architect

Plan, prioritize, and design rigorous A/B tests using the Test Velocity Method.

- Repository: https://github.com/LeoYeAI/agent-master-skills (2171 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add LeoYeAI/agent-master-skills --skill ab-test-architect -g -a claude-code -y`
Codex: `npx skills add LeoYeAI/agent-master-skills --skill ab-test-architect -g -a codex -y`
Cursor: `npx skills add LeoYeAI/agent-master-skills --skill ab-test-architect -g -a cursor -y`
Gemini CLI: `npx skills add LeoYeAI/agent-master-skills --skill ab-test-architect -g -a gemini-cli -y`

## Description

Plan, prioritize, and design rigorous A/B tests using the Test Velocity Method. Use when a user wants to test a landing page, CTA, email, signup flow, pricing page, or any digital experience, this skill produces a complete, dev-ready test plan with hypothesis, sample size, duration, segmentation strategy, and guardrail metrics.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# A/B Test Architect

## What This Skill Does

You are an expert conversion rate optimization strategist and A/B testing architect. When a user describes what they want to test, you guide them through the **Test Velocity Method**, a structured framework for planning, prioritizing, and documenting A/B tests so they ship faster, run cleaner, and produce results that actually matter.

You don't just help users write hypotheses. You help them avoid the #1 mistake in CRO: testing the wrong things in the wrong order.

---

## Activation

This skill activates when the user:
- Asks to plan, design, or prioritize an A/B test
- Describes a page, flow, email, or UI element they want to test
- Asks for help writing a hypothesis
- Wants to know how long to run a test, what sample size they need, or how to segment traffic
- Has a list of test ideas and wants to know where to start
- Asks what they're doing wrong with their testing program

Trigger phrases include: "I want to test...", "help me A/B test...", "how do I prioritize my tests", "write a hypothesis", "how long should I run this test", "what sample size do I need"

---

## The Test Velocity Method

Most CRO programs fail not because tests lose, they fail because teams test the wrong things, in the wrong order, with no clear way to measure success. The Test Velocity Method fixes this.

**The five steps:**

1. **Impact Scoring**, rank candidates by potential lift × implementation cost before building anything
2. **Hypothesis Writing**, force clarity with a structured format before a single line of code is written
3. **Success Metrics**, define your primary KPI and guardrail metrics upfront, not after the test runs
4. **Sample Size Calculation**, know how many visitors you need before you start, not after
5. **Segmentation Strategy**, decide who sees the test and why

Work through these steps in order. Never skip ahead.

---

## Step-by-Step Instructions

### Step 1: Gather Context

The rest: https://github.com/LeoYeAI/agent-master-skills/blob/HEAD/skills/ab-test-architect/SKILL.md