ab-test

Organize A/B tests with hypotheses, variants, metrics, and conclusions.

4|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ttorres33/project-docs --skill ab-test-ttorres33
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test
Source: https://github.com/ttorres33/project-docs/tree/main/skills/ab-test
Command: npx skills add https://github.com/ttorres33/project-docs --skill ab-test-ttorres33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents A/B tests with variants, hypothesis, measurement plan, and conclusions. Use when the user mentions running an A/B test, comparing two variants, or wanting to measure/test something systematically.

Core Features & Use Cases

  • Provides a structured scaffold to record test name, dates, hypotheses, variants, group assignment, metrics, results, and conclusions.
  • Enables governance, experiment planning, and learning preservation for product, marketing, and analytics teams.

Quick Start

Use concise prompts to document an A/B test by specifying a test-name and details for each section.

Frequently Asked Questions about ab-test

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

FAQPage Schema
How do I document A/B test hypotheses and measurement plans?

Document A/B test hypotheses and measurement plans by recording test names, dates, variants, group assignments, metrics, and conclusions in a structured scaffold. This preserves learning and enables experiment governance for analytics teams.

What is the best way to structure A/B test documentation for marketing experiments?

The best way to structure A/B test documentation for marketing experiments is to use a standardized scaffold capturing test name, dates, hypothesis, variants, metrics, results, and conclusions to ensure consistent governance across teams.

Can I use this to compare two variants systematically for product analysis?

Yes, you can use this to compare two variants systematically for product analysis. It provides a structured framework to record group assignments, measure outcomes, and document conclusions for product experiments.

What metrics should I track when running an A/B test?

When running an A/B test, track metrics defined in your measurement plan. Documenting these metrics alongside variants and hypotheses ensures outcomes are measured systematically and conclusions are preserved for future analysis.

Does A/B test documentation require any specific tools or dependencies?

No specific tools or dependencies are required to document A/B tests. You can record hypotheses, variants, group assignments, metrics, and conclusions using the structured scaffold without needing additional components or frameworks.

When should I not use a structured A/B test documentation format?

You should not use structured A/B test documentation when comparing more than two variants or when experiments lack defined hypotheses and measurement plans, as the scaffold is designed for two-variant comparisons with systematic outcome measurement.