AutoGineer
Generated banner for Brainstorm Experiments Existing
Generated logo for Brainstorm Experiments Existing

Brainstorm Experiments Existing

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill assists product teams in designing experiments to test assumptions for existing products. It focuses on identifying low-effort validation methods such as prototypes, feature stubs, and A/B tests to ensure feature ideas are viable before committing to full implementation. The skill emphasizes measuring actual user behavior over opinions and provides a structured approach to defining assumptions, metrics, and success thresholds.

What it does

  • Clarifies product ideas and underlying assumptions.
  • Suggests low-effort validation methods like fake door tests and technical spikes.
  • Defines clear metrics and success thresholds for experiments.
  • Provides guidance on risk mitigation for production-based testing.
  • Structures experiment plans for team review.

When to use it

  • When you need to validate assumptions for a new feature idea.
  • When planning product experiments for an existing product.
  • When you want to test feature ideas cheaply before full development.
  • When you need to move from opinion-based feedback to behavioral data.

Advantages

  • Reduces development waste by validating ideas early.
  • Focuses on behavioral data rather than subjective user opinions.
  • Encourages low-effort, high-learning experimental approaches.
  • Includes risk mitigation strategies for production tests.

Usage examples

“We want to add a subscription tier to our app but aren't sure if users will pay. How can we test this?”
The agent will suggest experiments like a fake door test or a landing page prototype to measure user interest through actual clicks before building the payment infrastructure.
“Design an experiment to see if users prefer a new navigation layout.”
The agent will propose a structured experiment plan, such as a prototype-based task completion test, including the specific metric to measure and the success threshold for the new layout.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/brainstorm-experiments-existing/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip brainstorm-experiments-existing.zip -d .agents/skills

Documentation by Pawel Huryn

Design Experiments (Existing Product)

Design low-effort experiments to test product assumptions before committing to full implementation.

Context

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.

Instructions

The user will describe their idea and assumptions. Work through these steps:

  1. Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.

  2. Suggest experiments for each assumption. Consider methods like:

    • First-click testing or task completion with a prototype

    • Feature stubs or fake door tests

    • Technical spikes

    • A/B tests on production (with risk mitigation)

    • Wizard of Oz approaches

    • Survey-based validation (behavioral, not opinion-based)

  3. Key principles to follow:

    • Measure actual behavior, not users' opinions

    • Test responsibly — don't put users or the business at risk

    • For production tests (e.g., A/B tests), explain risk mitigation strategies

    • Aim for maximum validated learning with minimal effort

  4. For each experiment, specify:

    • Assumption: What do we believe?

    • Experiment: What exactly will we do to validate it?

    • Metric: What will be measured?

    • Success threshold: The expected value if we are right

Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.

Further Reading

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "brainstorm-experiments-existing", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-product-discovery/skills/brainstorm-experiments-existing · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download brainstorm-experiments-existing.zip