brainstorm-experiments-existing

Design low-effort experiments to validate product assumptions.

Updated Mar 30, 2026

Search Tags:#prototyping #brainstorm #product-validation #experiments #hypothesis-testing #a/b-testing #rapid-learning

Ready to run

npx skills add https://github.com/omeragaakbas/zoyare --skill brainstorm-experiments-existing-omeragaakbas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorm-experiments-existing
Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/brainstorm-experiments-existing
Command: npx skills add https://github.com/omeragaakbas/zoyare --skill brainstorm-experiments-existing-omeragaakbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate product assumptions for an existing product using low-effort experiments. This guide helps teams plan cheap learning loops before committing to full-scale development.

Core Features & Use Cases

Clarify the idea and assumptions with stakeholders; leverage any available PRDs, designs, or notes to ground the experiments.
Propose a curated set of low-effort experiments (prototyping, fake-door tests, spikes, small-scale analytics, and lightweight pilots) with clear metrics and success criteria.
Apply to existing products to validate feature ideas, de-risk bets, and inform prioritization before heavy engineering.

Quick Start

Describe your idea and assumptions to generate a prioritized set of validated experiments.

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 product assumptions for an existing product without heavy engineering?▼

Validating product assumptions requires running low-effort experiments like fake-door tests, prototyping, and lightweight pilots to learn cheaply before committing to full-scale development.

What low-effort experiments can I run to test a new feature idea?▼

Low-effort experiments for feature validation include prototyping, fake-door tests, technical spikes, small-scale analytics, and lightweight pilots designed to capture clear metrics and success criteria.

How do I design a fake-door test to de-risk a product bet?▼

Designing a fake-door test involves clarifying your idea and assumptions with stakeholders, defining specific metrics, and setting decision thresholds to prioritize development based on rapid learning outcomes.

Can I use rapid learning experiments for feature prioritization on an existing product?▼

Rapid learning experiments apply to existing products to validate feature ideas, de-risk bets, and inform prioritization by leveraging available PRDs, designs, or notes to ground the experiment design.

What's the best way to define metrics and success criteria for a product validation spike?▼

Defining metrics for a product validation spike requires capturing clear assumptions upfront and establishing decision thresholds that guide prioritization before investing in heavy engineering efforts.

When should I avoid using low-effort experiments for hypothesis testing?▼

Avoid low-effort experiments when full-scale development is already committed, or when stakeholder assumptions cannot be clearly captured and grounded using available PRDs, designs, or notes for accurate metrics definition.