agentleFS
Sign inStart free
Adelie-SquadAdelie-Squad/solosquad/skills/experiment-design/SKILL.md

experiment-design

Skill25 starsChanged 9 days agoMITView on GitHub

Test spec + metric + gate 조건 + 기간 + variant 정의. data-analyst 의 Confidence Score 모델 입력 가설을 받아 manifest.yaml 생성.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use list-quality-scorecard and positive-reply-scoring.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • creatop-gtmSkill

    list-quality-scorecard

    Check a lead list before it goes into a sequence. Gives a deliverability readout (firm) and a targeting readout (advisory). Surfaces issues, never blocks. Use before enrolling any list.

    Also in 3 projects that use this

  • creatop-gtmSkill

    positive-reply-scoring

    Classify replies and compute positive reply rate, the metric that predicts revenue. Use to tell whether a campaign is actually working, not just getting replies.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Experiment Design Skill

Hypothesis-design 의 후속. recommended hypothesis 를 검증 가능한 실험으로 변환.

입력

  • recommended hypothesis (XYZ format) from skills/hypothesis-design
  • team OKR (어떤 KR 에 영향?)

산출 — <org>/experiments/<id>/manifest.yaml

experiment_id: exp-YYYY-MM-DD-<slug>
hypothesis:
  xyz: "[X%] of [Y] will [Z] within [T], because [R]"
  source_pr: "..."

variants:
  - id: control
    description: "current behavior"
    traffic_pct: 50
  - id: treatment
    description: "..."
    traffic_pct: 50

metrics:
  primary:
    name: "..."
    formula: "..."
    direction: increase | decrease
    threshold: "..."
  secondary: [...]
  guardrail: [...]

design:
  type: ab_test | feature_flag | concierge | wizard_of_oz | fake_door
  duration_days: 14
  min_sample: 1000
  power: 0.8
  alpha: 0.05

gates:
  start:
    - "instrumentation verified"
    - "guardrail metrics baselines stable"
  stop_early:
    - "guardrail breach"
    - "primary metric Δ p<0.01 (positive)"
  end:
    - "min_sample reached"
    - "duration reached"

evidence_refs:
  - "<org>/workflows/.../PRD.md"
  - "<org>/memory/open-questions/<task>.json"

≥ 2 Designs Rule

experiment design 도 항상 ≥2 후보:

  • AB test vs concierge MVP
  • feature flag vs cohort
  • 다른 traffic split

가장 cheap 한 valid design 우선 권고.

HARD GATE

- [ ] primary metric 1개 + threshold + window
- [ ] sample size 충분성 (power=0.8, α=0.05)
- [ ] guardrail metric ≥1 (regression 방지)
- [ ] start/stop/end gate 모두 정의
- [ ] product-designer 검토 (사용자 segment 차별 시)

Reference

  • phuryn/pm-skills/pm-execution/brainstorm-experiments
  • v1.1 PRD §12.3 (Experiment 인프라)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free