Experiment Designer

Design quick validation experiments for product features. Use this skill when the user needs to validate a hypothesis, test a feature idea before building, has low confidence in an initiative, or asks "should I build this" or "how do I validate this". Also trigger when user mentions prototypes, MVPs, testing, validation, or wants to reduce risk before investing in development. Guide them through choosing the right experiment method and defining success criteria.

9 stars 2 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Grafuja/Product-Manager-Skills --skill experiment-designer
Manual install
git clone --depth 1 https://github.com/Grafuja/Product-Manager-Skills.git /tmp/Product-Manager-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Product-Manager-Skills/skills/experiment-designer ~/.claude/skills/experiment-designer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Experiment Designer

Help product managers design lightweight validation experiments to test hypotheses before committing to full development.

## Core Philosophy

**Don't build to learn. Experiment to learn, then build.**

Experiments answer: "Should we build this?" before investing weeks/months.

---

## When to Use This Skill

Trigger experiment design when:
- Confidence < 70% on an initiative
- User asks "should we build X?"
- Feature is expensive (>4 weeks effort)
- Stakeholder request without user validation
- New product/market with uncertainty

**Don't experiment when:**
- Obvious must-have (e.g., fix critical bug)
- Feature already validated
- Regulatory requirement
- Confidence > 80% with solid data

---

## The Experiment Design Workflow

### Step 1: Capture the Hypothesis

Ask: **"What do you believe to be true that you want to test?"**

Help them form a clear hypothesis in IF-THEN format:

**Template:**
```
IF [we do X action],
THEN [Y measurable result will happen]
BECAUSE [assumption about users]
```

**Examples:**

✅ **Good hypothesis:**
"IF we show dashboard prototype to 10 CFOs,
THEN 8/10 will say they'd use it weekly
BECAUSE CFOs waste 30min/week on manual reports"

❌ **Bad hypothesis (too vague):**
"IF we build dashboard,
THEN users will like it"

**Push for specificity:**
- What EXACTLY are we testing?
- What EXACT result would confirm it?
- What's the underlying assumption?

**Store:** `hypothesis` (IF-THEN-BECAUSE statement)

---
Read the full skill on GitHub

Details

Skill name
experiment-designer
Path
skills/experiment-designer/SKILL.md
License
MIT
Repo updated
26 March 2026

FAQ

What does the Experiment Designer skill do?

Design quick validation experiments for product features. Use this skill when the user needs to validate a hypothesis, test a feature idea before building, has low confidence in an initiative, or asks "should I build this" or "how do I validate this". Also trigger when user mentions prototypes, MVPs, testing, validation, or wants to reduce risk before investing in development. Guide them through choosing the right experiment method and defining success criteria.

How do I install the Experiment Designer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Grafuja/Product-Manager-Skills --skill experiment-designer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Experiment Designer popular?

It lives in Grafuja/Product-Manager-Skills, which has 9 GitHub stars and 2 forks.

Related skills

Feature to Outcome

9

Grafuja/Product-Manager-Skills

Transform feature descriptions into outcome-oriented statements. Use this skill whenever the user has a feature/project described as an output (e.g., "build API", "create dashboard") and needs to reframe it as an outcome with measurable impact. Also trigger when user asks "how do I write this as an outcome", "turn this into a goal", or mentions OKRs, objectives, or outcome-based roadmaps. Help them articulate the problem, user, metric, and success criteria.

Data & Analytics

Rice Calculator Coach

9

Grafuja/Product-Manager-Skills

Interactive RICE (Reach, Impact, Confidence, Effort) calculator for product initiatives. Use this skill whenever the user wants to calculate RICE scores, prioritize features, rank initiatives, compare backlog items, or asks "how do I prioritize" or "what should I build first". Also trigger when user mentions RICE framework, scoring initiatives, or needs help with prioritization decisions. Guide them through each component step-by-step with examples and context.

Frontend & Design

Onboard Workshop

9

canonical/use-workshop-skill

Analyze an arbitrary repository and bootstrap a tailored Workshop definition from its existing build, test, and debug toolchain — feasibility verdict first, then propose, generate, launch, and verify. Use when a repo has no workshop definition yet and the user wants one derived from how the repo already builds and tests — "set up a workshop for this repo", "workshop-ify this project", "can this repo run in Workshop?".

Testing & QA

Spectacles 522 Portable Design

9

PtPavloTkachenko/spectacles-agent-skills

Design rules for building Spectacles lenses in Lens Studio 5.22 (CLAD/MCP workflow) so they downgrade to LS 5.15.4 for device testing in under an hour. Load when STARTING or architecting a new 5.22 Spectacles project that will later be tested on Spectacles (2024), when the user says "we will downgrade to 5.15" / "5.15-portable" / "we will test on device later", or before adding any shader/material/package to a 5.22 project that must survive the downgrade. Distilled from two full real-project migrations.

Testing & QA

Self Test Skill Invocation

9

konflux-ci/agent-plugins

Use when user asks to "test skill invocation framework" or mentions "canary skill test". This is a self-test skill to verify the test framework correctly loads and invokes skills.

Testing & QA18

Dpia Generator

9

wnallen/dpia-generator

Use whenever the user wants to run, draft, or stress-test a Data Protection Impact Assessment or any jurisdiction's equivalent for a new or modified processing. Triggers: "run a DPIA on", "assess privacy risk for", "is this Article 35 / high risk?", "need a Colorado data protection assessment / LGPD RIPD / PIPL PIPIA / Law 25 PIA?", any new-processing description (tool, vendor, AI feature, monitoring) with a privacy-risk question, or a pasted vendor page with a GDPR/ICO/CNIL/EDPB/CPPA/ANPD question. Also "index our privacy notice" — a portable notice profile later runs check for policy drift.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.