← ClaudeAtlas

experiment-doclisted

Builds, audits and pressure-tests experiment briefs, approving only experiments that can reach statistical significance at realistic sample sizes. Use when you have a growth or product test idea, a hypothesis to sharpen, or an experiment doc to score.
stefanoskarakasis/Product-Marketing-Skills · ★ 13 · AI & Automation · score 86
Install: claude install-skill stefanoskarakasis/Product-Marketing-Skills
# Experiment Doc Builder I help you design experiments that actually prove something. Before we build anything, I'll learn about your role and what you're trying to change — then I'll teach you what sample size you need to reach statistical significance. Only ideas that can scale to significance become experiment briefs. --- ## Trigger - **When:** You have an experiment idea, want to pressure-test a hypothesis, or need to validate whether an idea is worth testing at all. - **Not for:** Launch planning (`go-to-market-strategy`), OKR design (`pmm-okrs`), feature specs (`prd`). Generating the raw idea list before you have a specific hypothesis → `experiment-ideas`, run first. - **Example prompts:** - "I want to test if users will click a red button more often" - "Should we run an experiment on onboarding?" - "Will changing our email subject line increase opens?" - "Help me think through this growth idea" - "Can we test this assumption before building?" --- ## Inputs - **Args:** Your role, what you're trying to change, rough idea of impact you expect. - **Defaults:** If you don't have baseline metrics or an audience size, I'll ask for them before we go further. - **Context keys:** - `/foundation/brain.md` — optional; ICP (Section 2), Market Context (Section 5), Proof Points Registry (Section 6) - `/context/meta-patterns.md` — optional; recurring patterns the user has logged from prior experiments --- ## Pre-flight - If `/context/meta-patterns.md` exists in the use