brainstorm-experiments-existing

Coordinate low-effort experiments to validate product assumptions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/martiraste-lgtm/claude-skills --skill brainstorm-experiments-existing-martiraste-lgtm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm-experiments-existing
Source: https://github.com/martiraste-lgtm/claude-skills/tree/main/pm-product-discovery-brainstorm-experiments-existing
Command: npx skills add https://github.com/martiraste-lgtm/claude-skills --skill brainstorm-experiments-existing-martiraste-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design experiments to validate product assumptions for existing products using low-effort methods, enabling cheap testing of ideas and learning.

Core Features & Use Cases

  • Suggests a set of experiments per assumption (prototypes, fake doors, spikes, and lightweight A/B tests with risk mitigation).
  • Maps each idea to required validation metrics and decision criteria to de-risk product decisions.
  • Use Case: When validating a feature idea with limited resources, run a sequence of lightweight experiments to gather evidence quickly.

Quick Start

Describe your idea and assumptions, then outline 3–5 lightweight experiments to validate them.

Frequently Asked Questions about brainstorm-experiments-existing

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

FAQPage Schema
What is a low-effort experiment to validate product assumptions?

A low-effort experiment to validate product assumptions is a rapid learning method like a fake door test or lightweight prototype that gathers evidence cheaply before full development. It frames assumptions with measurable metrics and explicit success criteria to de-risk decisions.

How do I design lightweight experiments for existing product features?

To design lightweight experiments for existing product features, outline 3 to 5 validation methods such as prototypes, spikes, or lightweight A/B tests. Map each idea to required validation metrics and decision criteria to ensure rapid learning and risk mitigation.

When do I need to use fake door tests for product discovery?

You need to use fake door tests for product discovery when validating a feature idea with limited resources and rapid learning is required. They provide a low-effort method to measure user interest and gather evidence before committing to actual development.

Can I run lightweight A/B tests on existing products with limited resources?

Yes, you can run lightweight A/B tests on existing products with limited resources by framing them with clear assumptions and measurable metrics. This approach enables cheap testing of ideas and quick learning without heavy engineering investment.

What is the best way to map validation metrics to product assumptions?

The best way to map validation metrics to product assumptions is to define explicit success criteria and decision criteria for each experiment. This ensures that every prototype, spike, or fake door test directly de-risks your product decisions through measurable evidence.

Why do product experiments fail to de-risk product decisions?

Product experiments fail to de-risk product decisions when they lack clear assumptions, defined validation metrics, and explicit success criteria. Coordinating low-effort experiments with these elements ensures you gather actionable evidence to validate ideas properly.