brainstorm-experiments-new▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.
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
-
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
-
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
-
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
-
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 use brainstorm-experiments-new on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add brainstorm-experiments-new
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches brainstorm-experiments-new from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate brainstorm-experiments-new. Access the skill through slash commands (e.g., /brainstorm-experiments-new) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★75 reviews- ★★★★★Dhruvi Jain· Dec 24, 2024
brainstorm-experiments-new is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kiara Ghosh· Dec 16, 2024
brainstorm-experiments-new has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Michael Srinivasan· Dec 12, 2024
Keeps context tight: brainstorm-experiments-new is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Layla Abebe· Dec 8, 2024
Useful defaults in brainstorm-experiments-new — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Zara Taylor· Dec 8, 2024
brainstorm-experiments-new fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kabir Johnson· Dec 8, 2024
brainstorm-experiments-new reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Advait Yang· Nov 27, 2024
brainstorm-experiments-new is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ren Ghosh· Nov 27, 2024
We added brainstorm-experiments-new from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kiara White· Nov 27, 2024
Registry listing for brainstorm-experiments-new matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Oshnikdeep· Nov 15, 2024
Useful defaults in brainstorm-experiments-new — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 75