brainstorm-experiments-existing
by phurynbrainstorm-experiments-existing helps you design low-effort experiments for an existing product, including prototypes, fake-door tests, A/B tests, technical spikes, Wizard of Oz flows, and behavioral surveys. Use it to validate assumptions, reduce risk, and decide what to build next. This brainstorm-experiments-existing guide is built for practical product validation and Workflow Automation support.
This skill scores 78/100, which means it is a solid listing candidate for directory users. It clearly tells an agent when to trigger it, gives a useful experiment-design workflow, and is more actionable than a generic prompt for product validation. Users should still expect some limitations because the repo is lightweight and lacks supporting assets or scripts, but the core guidance is strong enough to justify install consideration.
- Clear triggerability: the description explicitly targets existing-product assumption validation and experiment planning.
- Operational workflow is present: it outlines step-by-step guidance for clarifying assumptions, suggesting experiments, and defining outputs per experiment.
- Good agent leverage: includes concrete experiment types like fake doors, prototypes, technical spikes, A/B tests, Wizard of Oz, and behavioral surveys.
- Lightweight repo: no scripts, references, resources, or supporting files, so adoption depends mostly on the single SKILL.md.
- Experimental/test-like signal lowers trust slightly; users should verify fit if they need stricter governance or richer examples.
Overview of brainstorm-experiments-existing skill
brainstorm-experiments-existing is a workflow-focused skill for designing low-effort experiments against an existing product before you commit engineering time. It helps you turn a feature idea and a set of assumptions into testable options such as prototypes, fake-door tests, A/B tests, technical spikes, Wizard of Oz flows, or behavioral surveys. The main job-to-be-done is simple: reduce uncertainty fast while avoiding risky overbuild.
Who this skill is best for
Use the brainstorm-experiments-existing skill when you already have a product, a proposed change, and at least one question you need answered. It fits product managers, designers, founders, and engineers who need a practical brainstorm-experiments-existing guide for validating scope, demand, usability, or technical feasibility.
What makes it different
This skill is not a generic ideation prompt. It pushes for experiments that measure behavior, not just opinions, and it asks you to think about risk mitigation when tests touch production. That makes brainstorm-experiments-existing for Workflow Automation useful when your workflow needs decision support rather than a broad list of feature ideas.
When it is a good fit
Choose this skill if you need the brainstorm-experiments-existing skill to help you decide “should we build this, and how should we test it cheaply first?” It is strongest when you can name the assumptions you want to validate and you care about learning speed, cost, and user safety.
How to Use brainstorm-experiments-existing skill
Install and point it at real context
Use the brainstorm-experiments-existing install path in your skills manager, then feed the skill the most relevant source material you already have: PRD notes, assumption lists, design mockups, support tickets, or a rough feature brief. The skill is designed to work from $ARGUMENTS, so the clearer your input, the better the experiment plan.
Turn a vague idea into a usable prompt
A weak prompt says, “Help us test a new onboarding feature.” A stronger prompt says, “We want to add team-based onboarding to improve activation for SMB admins. Assume the key risks are discoverability and completion time. Propose 3 experiments with lowest-effort validation first, and note what success looks like for each.”
That style works because it gives the brainstorm-experiments-existing usage flow a specific product area, a target user, and a measurable assumption.
Read the repo in the right order
Start with SKILL.md, because it contains the core workflow and output expectations. If your local copy includes supporting docs, inspect README.md, AGENTS.md, metadata.json, and any rules/, resources/, references/, or scripts/ folders next. In this repository, the skill is compact and support files are minimal, so most of the value is in understanding the main instruction file well.
Shape the output for better decisions
Ask the skill to organize results by assumption, experiment type, cost, risk, and expected signal. When possible, include constraints such as “no production risk,” “one-week timeline,” or “no design resources available.” Those details help the brainstorm-experiments-existing guide produce experiments you can actually ship, not just interesting theory.
brainstorm-experiments-existing skill FAQ
Is this just a brainstorming prompt?
No. The brainstorm-experiments-existing skill is about structured validation for an existing product, not open-ended ideation. It is most useful when you need experiments that can falsify assumptions, not a long list of creative possibilities.
When should I not use it?
Skip this skill if you do not yet know the product problem, the target user, or the assumption under test. It is also a poor fit when you need implementation planning, not validation, or when the idea is so early that you need discovery interviews before experiments.
Can beginners use it?
Yes, as long as they can describe the product idea in plain language. Beginners get the most value when they supply a rough goal, a user segment, and a suspected risk. That lets the brainstorm-experiments-existing skill convert uncertainty into concrete test options.
How does it fit Workflow Automation?
Use brainstorm-experiments-existing for Workflow Automation when you want an automated assistant to propose validation steps, compare experiment types, or keep a team aligned on evidence-gathering. It is less useful for automating execution of the experiment itself than for designing the test plan.
How to Improve brainstorm-experiments-existing skill
Give the skill sharper assumptions
The biggest quality jump comes from naming the assumption precisely. Instead of “Will users like it?” provide “Will first-time admins find the new bulk-invite flow without help?” The brainstorm-experiments-existing skill can then map each assumption to a lower-cost experiment with a clear signal.
Add constraints that change the experiment
Include timeline, risk tolerance, available traffic, and tooling limits. For example: “We can only test in staging,” “We have one sprint,” or “We can use existing analytics but not new tracking.” Those constraints force the brainstorm-experiments-existing guide to recommend realistic experiments rather than ideal ones.
Ask for decision-ready output
Request a format that includes assumption, experiment, signal, risk, and next step. That makes it easier to compare options and prevents vague recommendations. If the first pass is too broad, iterate by asking for fewer experiments, stronger falsification criteria, or a shortlist ranked by effort versus confidence gained.
Improve the prompt after the first pass
If the result is generic, add more context about the current product behavior, the user journey, and what would count as success or failure. The brainstorm-experiments-existing install is most valuable when you treat it like a validation copilot: feed it your real constraints, then refine the plan until each experiment would justify a build/no-build decision.