Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add phuryn/pm-skills --skill "brainstorm-experiments-new" -g -a claude-code -yOr manually — copy the SKILL.md below into:
~/.claude/skills/brainstorm-experiments-new/SKILL.md---
name: brainstorm-experiments-new
description: "Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand."
---
## Design Lean Startup Experiments (New Product)
Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.
### Context
You are helping validate a new product concept: **$ARGUMENTS** using lean startup methodology.
If the user provides files (market research, landing page mockups), read them first.
### Instructions
1. **Create an XYZ Hypothesis** in the form: "At least X% of Y will do Z"
- **X%**: The percentage of the target market expected to engage
- **Y**: The specific target market (e.g., "mid-size luxury sedan buyers")
- **Z**: How they will engage with the product
2. **Suggest 2-3 pretotype experiments** to test the hypothesis with minimal effort. Consider:
- **Landing Page**: Test interest by measuring sign-ups or clicks
- **Explainer Video**: Test understanding and appeal through engagement metrics
- **Email Campaign**: Test demand through response and click-through rates
- **Pre-Order / Waitlist**: Test willingness to pay through skin-in-the-game commitment
- **Concierge / Manual MVP**: Deliver the service manually to test value
3. **Key principles** (Alberto Savoia, *The Right It*):
- **Skin-in-the-Game**: Test willingness to pay — not just interest. Real commitment (time, money, reputation) is the only reliable signal.
- **Your Own Data (YODA)**: Collect your own data through experiments rather than relying on Others' Data (ODP) like market reports or analogies. "The market for your idea does not care about the market for someone else's idea."
- Measure actual behavior, not users' opinions
4. **For each experiment**, specify the hypothesis being tested, the method, the metric, and the success threshold.
Think step by step. Save as markdown if substantial.
---
### Further Reading
- [How to Build the Right Product with Alberto Savoia (ex-Innovator at Google)](https://www.productcompass.pm/p/how-to-build-the-right-product-with)
- [Testing Product Ideas: The Ultimate Validation Experiments Library](https://www.productcompass.pm/p/the-ultimate-experiments-library)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code