brainstorm-experiments-new
by phurynbrainstorm-experiments-new helps Product Management teams design lean startup validation experiments for a new product idea. It creates an XYZ hypothesis and suggests low-effort tests like landing pages, explainer videos, email campaigns, pre-orders, waitlists, and concierge MVPs to validate demand before building.
This skill scores 78/100 and is worth listing: it gives agents a clear trigger, a concrete lean-startup workflow, and specific experiment types for validating a new product idea. For directory users, that means it should reduce guesswork versus a generic prompt, though it is still a focused, single-purpose skill rather than a broad discovery toolkit.
- Clear use case and triggerability: the description says to use it for validating a new product idea, creating pretotypes, or testing market demand.
- Operational workflow is concrete: it instructs the agent to create an XYZ hypothesis and propose 2-3 low-effort experiments such as landing pages, explainer videos, email campaigns, waitlists, or concierge/manual MVPs.
- Good install decision value for product discovery work: the body is substantial (2207 chars) and the frontmatter is valid, so users can quickly tell what problem it solves and how it should behave.
- No supporting scripts, references, or resources are included, so the guidance appears self-contained and may need user judgment for implementation details.
- The skill is narrowly scoped to new-product experimentation and pretotype validation, so it is not a general product-research skill.
Overview of brainstorm-experiments-new skill
What brainstorm-experiments-new does
The brainstorm-experiments-new skill helps you design lean startup validation experiments for a new product idea. It turns a rough concept into an XYZ hypothesis and a small set of low-effort tests, such as a landing page, explainer video, email campaign, pre-order, or concierge MVP.
Who should use it
Use the brainstorm-experiments-new skill for Product Management when you need to decide whether an idea is worth building, refine a value proposition, or pressure-test demand before investing in a full MVP. It is most useful for early-stage founders, PMs, and product teams working with uncertain market fit.
What makes it useful
The main value is speed with structure: the skill pushes you toward a clear hypothesis, a practical experiment mix, and a bias toward evidence over opinion. That is better than a generic brainstorm because it focuses on testable demand signals, especially skin-in-the-game behaviors like sign-ups, pre-orders, or replies.
How to Use brainstorm-experiments-new skill
Install and trigger it
Install the brainstorm-experiments-new skill with npx skills add phuryn/pm-skills --skill brainstorm-experiments-new. Then invoke it with the product concept you want to validate, plus any context that changes the test design: target user, problem, pricing, channel, or constraints.
Give the skill a complete input
Strong prompts describe the idea, not just the category. For example, instead of “validate my app,” use: “Validate a B2B AI note-taking tool for solo consultants who lose time after client calls; test demand before building.” The more specific the target market and desired behavior, the better the XYZ hypothesis and experiment choices.
Start with the right files
The repository’s core guidance lives in SKILL.md, so read that first. If your workspace includes attached research, mockups, or prior notes, supply those before asking for experiments. The skill explicitly says to read user-provided files first, which helps it anchor experiments in real context instead of generic startup advice.
Use a workflow that matches the output
A practical brainstorm-experiments-new usage flow is: define the problem, state the target audience, ask for an XYZ hypothesis, then request 2–3 experiments ranked by effort and signal quality. If you care about a specific signal, say so up front, such as “focus on willingness to pay” or “optimize for speed of learning rather than conversion volume.”
brainstorm-experiments-new skill FAQ
Is brainstorm-experiments-new only for new products?
It is best for new product concepts and early validation, but you can also use it for feature ideas, repositioning, or demand testing before a launch. If you already have strong usage data and a working product, a different analysis skill may be more appropriate than brainstorm-experiments-new.
How is this different from a normal prompt?
A normal prompt may give you a list of ideas; the brainstorm-experiments-new skill gives you a repeatable lean-testing structure. It is especially useful when you want a hypothesis you can defend and experiments that reveal actual market interest, not just plausible-sounding concepts.
Is it beginner-friendly?
Yes, as long as you can describe the product idea in plain language. The biggest beginner mistake is staying too vague. The skill works better when you name the audience, problem, and the behavior you want to observe, even if your idea is still rough.
When should I not use it?
Do not use brainstorm-experiments-new if your question is about implementation details, technical architecture, or post-launch optimization. It is not a build-plan generator; it is a validation-planning skill for deciding what to test first and how to test it cheaply.
How to Improve brainstorm-experiments-new skill
Provide sharper market context
The most important improvement is specificity. Include the user segment, pain point, current workaround, and any constraint that shapes the test, such as budget, timeline, or channel. For brainstorm-experiments-new for Product Management, “small marketing agencies that need faster client reporting” is much better than “business users.”
Ask for experiments with different signal strength
Good inputs help the skill choose tests that measure more than curiosity. If you want stronger evidence, ask for one low-friction interest test and one commitment test, such as a landing page plus a pre-order or waitlist. That combination reduces the risk of mistaking clicks for demand.
Watch for the common failure mode
The main failure mode is a vague hypothesis that cannot be falsified. If the output says “people will like it,” push it to express a measurable threshold, audience, and action. A better brainstorm-experiments-new guide prompt is: “Create an XYZ hypothesis for enterprise HR managers who need faster onboarding, and propose tests that show willingness to pay within two weeks.”
Iterate after the first pass
Use the first output to pick the cheapest credible test, then refine based on what you learn. If the idea is interesting but the signal is weak, narrow the audience or change the behavior you measure. If the concept is unclear, ask brainstorm-experiments-new to rewrite the hypothesis around a single user segment and a single promised outcome.