Help us improve
Share bugs, ideas, or general feedback.
From pm-product-discovery
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.
npx claudepluginhub tarunccet/pm-skills --plugin pm-product-discoveryHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-product-discovery:brainstorm-experiments-existingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design low-effort experiments to test product assumptions before committing to full implementation.
Designs low-effort experiments like prototypes, A/B tests, spikes, and Wizard of Oz to validate assumptions and test feature ideas for existing products.
Defines testable hypotheses with success metrics, target users, and validation approaches. Use for experiments, A/B tests, and aligning teams on assumptions.
Designs smallest viable tests to validate or invalidate critical assumptions using Torres framework and Gilad's AFTER model (Assessment to Release Results).
Share bugs, ideas, or general feedback.
Design low-effort experiments to test product assumptions before committing to full implementation.
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.
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:
Key principles to follow:
For each experiment, specify:
Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.