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 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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/brainstorm-experiments-existing · pinned to the source commit
# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-product-discovery/skills/brainstorm-experiments-existing" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-product-discovery/skills/brainstorm-experiments-existing" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/brainstorm-experiments-existing
Scanner static-checks@0.1.0 · commit 18468a95b427. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.