brainstorm-experiments-existing
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.
Works with
--- name: brainstorm-experiments-existing description: 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. license: MIT --- ## 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 - [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library) - [Assumption Prioritization Canvas: How to Identify And Test The Right Assumptions](https://www.productcompass.pm/p/assumption-prioritization-canvas) - [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

