brainstorm-experiments-existing
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.
Security Assessment
About brainstorm-experiments-existing
brainstorm-experiments-existing helps a product team design low-effort experiments to validate assumptions for an existing product before committing to full implementation. It is used when validating assumptions, testing feature ideas cheaply, or planning product experiments, with the aim of maximum validated learning at minimal effort. The user describes their feature idea and the assumptions that need validation, and if they provide files such as PRDs, assumption lists, or designs, the skill reads them first.
The skill works through a clear sequence. It first clarifies the idea and the assumptions to confirm what the team wants to build and validate. It then suggests experiments for each assumption, drawing on methods including 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, and behavioral (not opinion-based) survey validation. It follows key principles: measure actual behavior rather than opinions, test responsibly without putting users or the business at risk, explain risk mitigation for production tests, and aim for maximum validated learning with minimal effort. For each experiment it specifies the Assumption (what is believed), the Experiment (exactly what will be done), the Metric (what will be measured), and the Success threshold (the expected value if the belief is right), presenting the experiments in a clear table or structured format and saving as markdown if substantial.
The skill targets product managers and discovery teams who already have a feature idea and a set of assumptions and want cheap, responsible validation methods. Documented in a single SKILL.md, it takes the product context via $ARGUMENTS and points to further reading including an experiments library, an assumption prioritization canvas, and product discovery guides. It emphasizes behavior over opinion and responsible testing as its guardrails rather than depending on any specific tooling.
FAQ
What experiment methods does it suggest?
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, and survey-based validation that measures behavior rather than opinion.
What does it specify for each experiment?
For each experiment it defines the Assumption (what the team believes), the Experiment (exactly what will be done to validate it), the Metric (what will be measured), and the Success threshold (the expected value if the assumption is right).
What guiding principles does it follow?
Measure actual behavior rather than users' opinions, test responsibly without putting users or the business at risk, explain risk mitigation strategies for production tests such as A/B tests, and aim for maximum validated learning with minimal effort.
How do I provide input and receive output?
You describe your idea and assumptions (passed via $ARGUMENTS), optionally providing files like PRDs, assumption lists, or designs which the skill reads first. Experiments are presented in a clear table or structured format and saved as markdown if substantial.
Install brainstorm-experiments-existing
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
phuryn/pm-skills