Product Experiment Designer

Brainstorm experiments existing

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

---
name: brainstorm-experiments-existing
description: "Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments."
---

## Design Experiments (Existing Product)

Design low-effort experiments to test product assumptions before committing to full implementation.

### Context

You are helping a product team design experiments for **$ARGUMENTS**. The team has a feature idea and assumptions that need validation.

If the user provides files (PRDs, assumption lists, designs), read them first.

### Instructions

The user will describe their idea and assumptions. Work through these steps:

Overview

Design low-effort experiments to test product assumptions before committing to full implementation.

Manual install (npx, ZIP)

Claude Codenpx skills add phuryn/pm-skills --skill brainstorm-experiments-existing -g -a claude-code

Claude Code (degit)

npx degit phuryn/pm-skills/pm-product-discovery/skills/brainstorm-experiments-existing#main ~/.claude/skills/brainstorm-experiments-existing

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.4 KB

Read SKILL.md here

phuryn/main1 file shown

SKILL.md2.4 KB

Browse every file on GitHub↗

SKILL.md

Show the full text52 lines

brainstorm-experiments-existing/SKILL.md52 lines · 2.4 KB

PreviewCode

Outline

RawView on GitHub

Design Experiments (Existing Product)

Design low-effort experiments to test product assumptions before committing to full implementation.

Context

You are helping a product team design experiments for $ARGUMENTS. The team has a feature idea and assumptions that need validation.

If the user provides files (PRDs, assumption lists, designs), read them first.

Instructions

The user will describe their idea and assumptions. Work through these steps:

Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
Suggest experiments for each assumption. Consider methods like:
- First-click testing or task completion with a prototype
- Feature stubs or fake door tests
- Technical spikes
- A/B tests on production (with risk mitigation)
- Wizard of Oz approaches
- Survey-based validation (behavioral, not opinion-based)
Key principles to follow:
- Measure actual behavior, not users' opinions
- Test responsibly — don't put users or the business at risk
- For production tests (e.g., A/B tests), explain risk mitigation strategies
- Aim for maximum validated learning with minimal effort
For each experiment, specify:
- Assumption: What do we believe?
- Experiment: What exactly will we do to validate it?
- Metric: What will be measured?
- Success threshold: The expected value if we are right

Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.

1	---
2	name: brainstorm-experiments-existing
3	description: "Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments."
4	---
5
6	## Design Experiments (Existing Product)
7
8	Design low-effort experiments to test product assumptions before committing to full implementation.
9
10	### Context
11
12	You are helping a product team design experiments for $ARGUMENTS. The team has a feature idea and assumptions that need validation.
13
14	If the user provides files (PRDs, assumption lists, designs), read them first.
15
16	### Instructions
17
18	The user will describe their idea and assumptions. Work through these steps:
19
20	1. Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
21
22	2. Suggest experiments for each assumption. Consider methods like:
23	- First-click testing or task completion with a prototype
24	- Feature stubs or fake door tests
25	- Technical spikes
26	- A/B tests on production (with risk mitigation)
27	- Wizard of Oz approaches
28	- Survey-based validation (behavioral, not opinion-based)
29
30	3. Key principles to follow:
31	- Measure actual behavior, not users' opinions
32	- Test responsibly — don't put users or the business at risk
33	- For production tests (e.g., A/B tests), explain risk mitigation strategies
34	- Aim for maximum validated learning with minimal effort
35
36	4. For each experiment, specify:
37	- Assumption: What do we believe?
38	- Experiment: What exactly will we do to validate it?
39	- Metric: What will be measured?
40	- Success threshold: The expected value if we are right
41
42	Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.
43
44	---
45
46	### Further Reading
47
48	- [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library)
49	- [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas)
50	- [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery)
51	- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
52