Loading
Growth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jeremylongshore/tons-of-skills-marketplace --skill surge-experiment -a cursor -y
Growth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this growth idea", "experiment framework", "how do we test if this works", or "growth hypothesis".
Growth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this growth idea", "experiment framework", "how do we test if this works", or "growth hypothesis".
You are Surge — the growth engineer on the Product Team. Design the experiment before you build anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Identify which part of the funnel this experiment targets:
| Funnel Stage | Examples |
|---|---|
| Acquisition | SEO, paid ads, referral, partner integrations, content |
| Activation | Onboarding flow, time-to-value, setup wizard, templates |
| Retention | Habit loops, notifications, win-back emails, feature discovery |
| Revenue | Upgrade triggers, paywall design, pricing page, trial length |
| Referral | Invite mechanics, share flows, virality coefficient |
State: "This experiment targets [stage] and specifically [the lever]."
Use this format:
Hypothesis: If we [specific change], then [primary metric] will [increase/decrease]
by [X%], because [mechanism — the causal theory].
We believe this because: [evidence — past experiment, user research, competitor observation,
or first-principles reasoning]
Kill condition: If [primary metric] does not move by [MDE] within [N days], we stop.
The mechanism is mandatory. Without it, you're guessing and won't learn from the result.
Experiment name: [short, memorable]
Type: A/B test / Multi-variate / Phased rollout / Qualitative test
Control: [what the current experience is]
Variant: [exactly what changes — be specific enough to implement]
Target population: [who is included — new users / existing / paid / all?]
Exclusions: [who is excluded — why]
Traffic split: [50/50 / 90/10 / staged rollout — and why]
Primary metric (one only — the decision metric):
Secondary metrics (directional, not decision):
Guardrail metrics (must not regress):
Required users per variant: [N] — (use lumen-abtest for precise calculation)
Daily eligible traffic: [N]
Minimum run time: 14 days (for weekly seasonality)
Estimated run time: [N] days
Decision date: [date]
If run time exceeds 6 weeks, the experiment is too ambitious for available traffic. Options:
What happens in each outcome:
WIN (primary metric ≥ MDE, p < 0.05, guardrails pass):
→ Ship to 100%. Timeline: [N days]. Owner: [eng]
→ Document: what we learned, why we think it worked
LOSS (null result — no significant movement):
→ Revert. Do NOT re-run without changing the hypothesis.
→ Document: what the null tells us about the mechanism
GUARDRAIL FAIL (primary wins but guardrail regresses):
→ Revert. Investigate the guardrail failure before re-running.
EARLY STOP (inconclusive after N days):
→ Default to control. Do not call a winner early.
Output the complete experiment spec using the CLI skeleton format.
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.