Skip to content
cccskills
FreePublished on GitHub

product-experiment-design

Use when the user names an A/B test, an experiment, a growth bet, or a before-and-after read: the plan with one primary metric, guardrails, a computed sample size, precommitted interpretation bands, then the scale-extend-or-kill readout.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Product experiment design

Use this when the user names an A/B test, an experiment, a growth bet, or a before-and-after read. The output is a plan whose verdict is decided before the data arrives, and then the readout against it.

What you need first

The belief under test, the decision it informs, and the traffic or users available. No traffic numbers means you size with bands and name the minimum sample before launch. No belief stated means you name the bottleneck belief first and get a yes on it.

Design it

  1. Name the one bottleneck belief the test exists to move. A test that tries to prove three things proves none.
  2. List two to four candidate tests and compare them on information gain, cost, time, and reversibility. Pick one and say in a line why it won.
  3. Write the design: control and variant; ONE primary success metric; guardrail metrics that catch harm elsewhere; the minimum sample computed from the baseline plus the minimum detectable effect at 95% significance and 80% power; a duration of at least one to two full weeks; pre-declared segments; the business-meaningful threshold stated beside the p-value; and the flag configuration. Guardrails are not optional.
  4. Precommit the interpretation bands with observable numbers: the upgrade band where you scale, the ambiguous band where you extend or rethink, and the downgrade band where you kill. No vague words like "several" or "good".
  5. State plainly what the test cannot establish, then launch only on a yes.
  6. Read it out: the band it landed in, the guardrail check, the sample-ratio mismatch check, and the call — scale, extend, or kill.

Output

The dated experiment plan and, after the run, the dated readout with the call and the follow-up offered on a yes.

When the traffic is not there

Say the sample will not reach the minimum and propose the alternative — a longer run, a bigger effect to look for, a painted-door test, or a qualitative read instead. Never move the bands after seeing the data, and never call a test before one to two full weeks and the precomputed sample size.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill