/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.
One skill from pm-skills.
shell
$ npx -y skills add phuryn/pm-skills --skill brainstorm-experiments-existing --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/brainstorm-experiments-existing
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
Stats
Stars24,318
Forks2,501
LicenseMIT
SKILL.md
brainstorm-experiments-existing.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**: