brainstorm-experiments-existing

Name: brainstorm-experiments-existing
Author: phuryn

1.7kinstalls2.5kforks

How to install brainstorm-experiments-existing?

phuryn/pm-skills/brainstorm-experiments-existing

$npx -y skills add phuryn/pm-skills --skill brainstorm-experiments-existing

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type

brainstorm-experiments-existing

1.7kinstalls2.5kforks

View on GitHub

How to install brainstorm-experiments-existing?

phuryn/pm-skills/brainstorm-experiments-existing

$npx -y skills add phuryn/pm-skills --skill brainstorm-experiments-existing

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type