cro-sprint

Use when running a CRO iteration cycle — diagnose top conversion bottleneck, design experiment, build variant, run A/B test, analyze results, ship or iterate. Also use when the user says “CRO sprint” or “conversion experiment”.

Model	Source
sonnet	pack: seo

Full Reference

CRO Sprint

A 4-week orchestrator for a single, disciplined CRO experiment — from bottleneck diagnosis to shipping or iterating. One sprint = one hypothesis, one test, one decision. After each sprint closes, start the next with the next bottleneck from the cro-audit priority list.

Quick Reference

Week	Phase	Skills Invoked	Output
1	Diagnose	cro-audit, microsoft-clarity, landing-page-cro	Hypothesis document
1–2	Design	ab-testing	Sample size, test duration, success criteria
2	Build	ab-testing, posthog	Variant live behind feature flag
2–4	Run	ab-testing	SRM checks, guardrail monitoring
4	Decide	ab-testing	Results document, next sprint

Item	Value
Sprint duration	4 weeks
Velocity target	One completed sprint every 4 weeks
Variables per test	1 — never test two changes at once
SRM tolerance	±5% of 50/50 split — restart if exceeded
Early stop threshold	99.5% confidence only (p < 0.005)
Sprint selection: min traffic	≥ 50 daily sessions on test page
Hypothesis file location	.claude/progress/experiments/[test-name]-hypothesis-[date].md
Results file location	.claude/progress/experiments/[test-name]-results-[date].md

Reference Index

I want to…	File
Write a hypothesis, build a results doc, understand sprint workflow and decision framework	reference/experiment-templates.md

Usage: Read the reference file matching your current task from the index above. Each file is self-contained with code examples and inline gotchas.

---

Announcement

┏━ 🎯 cro-sprint ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ 4-week CRO experiment cycle — diagnose, design, ┃ ┃ build, run, and decide on one hypothesis ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛