Brainstorm Experiments Existing
Added March 10, 2026 Source: Pawel Huryn
Planning to add a new feature to an existing product? Design low-effort experiments to quickly validate your assumptions before committing to full development. Get ideas for prototypes, A/B tests, and other validation methods.
Installation
This skill is self-contained. Copy the SKILL.md below directly into your project to get started.
.claude/skills/brainstorm-experiments-existing/SKILL.md # Claude Code
.cursor/skills/brainstorm-experiments-existing/SKILL.md # CursorOr install as a personal skill (available across all your projects):
~/.claude/skills/brainstorm-experiments-existing/SKILL.mdYou can also install using the skills CLI:
npx skills add phuryn/pm-skills --skill brainstorm-experiments-existingRequires Node.js 18+.
SKILL.md
---
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:
1. **Clarify the idea and assumptions**: Confirm what the team wants to build and what they need to validate.
2. **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)
3. **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
4. **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.
---
### Further Reading
- [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library)
- [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas)
- [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Originally by Pawel Huryn, adapted here as an Agent Skills compatible SKILL.md.
This skill follows the Agent Skills open standard, supported by Claude Code, Cursor, Codex, Gemini CLI, and 20+ more editors.
Works with
Agent Skills format — supported by 20+ editors. Learn more