Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.
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.
Review the instructions the agent will receive before you install.
Design low-effort experiments to test product assumptions before committing to full implementation.
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.
The user will describe their idea and assumptions. Work through these steps:
Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
Suggest experiments for each assumption. Consider methods like:
Key principles to follow:
For each experiment, specify:
Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.
Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.
Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.
Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.
Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.
Generate improvement ideas for an existing product from product management, design, and engineering perspectives. Produce five ideas per perspective, then select the top five based on goals, potential impact, feasibility, and differentiation, with reasons and assumptions to test.