brainstorm-experiments-existing

Designs low-cost experiments to validate product hypotheses for existing products.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill brainstorm-experiments-existing-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm-experiments-existing
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-product-discovery/skills/brainstorm-experiments-existing
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill brainstorm-experiments-existing-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often commit to full development before knowing whether a feature idea will work. This Skill helps you design low-investment experiments—prototypes, A/B tests, fake door tests, technical spikes—to validate assumptions before writing production code. ## Core Features & Use Cases - Hypothesis-to-Experiment Mapping: Suggests concrete validation methods for each assumption, including first-click testing, fake door tests, Wizard of Oz, technical spikes, and production A/B tests. - Structured Experiment Specs: For every experiment, defines the hypothesis, method, metrics, and success threshold in a clear table or structured format. - Risk-Aware Testing Guidance: Emphasizes measuring real behavior over opinions and includes risk mitigation strategies for production tests. - Use Case: A PM believes a new onboarding flow will improve activation. Use this Skill to design a fake door test measuring click-through on the new entry point, with a defined success threshold, before building anything. ## Quick Start Ask the AI to design low-cost experiments to validate the assumptions behind your feature idea, describing your product context and the hypotheses you need to test.

Frequently Asked Questions about brainstorm-experiments-existing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a product idea before building it?

Design low-investment experiments such as fake door tests, prototype first-click tests, or Wizard of Oz studies. Define the hypothesis, the experiment method, the metric to measure, and a success threshold before running the test.

What experiments can test product assumptions cheaply?

Common low-cost methods include fake door tests, first-click testing on prototypes, technical spikes, Wizard of Oz simulations, and behavior-based surveys. Each measures real user behavior rather than stated opinions.

How do I run an A/B test without risking users or revenue?

Pair production A/B tests with explicit risk mitigation strategies, such as limiting exposure to a small user segment and defining rollback criteria. The experiment spec should state the hypothesis, metric, and success threshold upfront.

When should I use a fake door test versus a prototype test?

Use a fake door test to measure demand for a feature that does not exist yet, via clicks on a placeholder entry point. Use prototype first-click or task-completion tests to validate usability of a proposed flow before development.

Why measure behavior instead of user opinions in experiments?

Stated opinions often diverge from actual behavior, making surveys unreliable for validation. Behavioral metrics like clicks, task completion, and conversion reveal what users truly do, producing stronger evidence for product decisions.