brainstorm-ideas-new
by phurynbrainstorm-ideas-new is a discovery-stage ideation skill for turning a new product concept into specific feature ideas from PM, Designer, and Engineer perspectives. Use it for initial product discovery, startup ideas, and Strategic Planning when you need practical options to validate before building.
This skill scores 71/100 and is worth listing because it has a clear initial-discovery use case, a readable multi-perspective workflow, and enough detail for an agent to trigger and follow it with less guesswork than a generic brainstorm prompt. For directory users, that means it is installable and practically useful, but not yet a highly polished or deeply instrumented workflow.
- Clear trigger and scope for initial product discovery from PM, designer, and engineer perspectives
- Concrete stepwise workflow: understand the opportunity, then generate 5 ideas each from three viewpoints
- Frontmatter is valid and the body is substantive, with no placeholder markers or experimental/test-only signals
- No supporting scripts, references, resources, or install command, so operational depth and trust signals are limited
- The excerpt shows a truncated engineer section and there is little evidence of edge-case handling or examples
Overview of brainstorm-ideas-new skill
brainstorm-ideas-new is a discovery-stage ideation skill for turning a rough new-product concept into concrete feature ideas from PM, Designer, and Engineer perspectives. It is best for teams doing initial product discovery when they need to decide what a product could be, who it serves, and which directions are worth validating before building.
Use the brainstorm-ideas-new skill when you want more than generic brainstorming. It is designed to surface ideas that are specific enough to evaluate, compare, and turn into follow-up research or MVP scope. It is a strong fit for startup concepts, new product bets, and early feature exploration for Strategic Planning.
What it does best
The skill pushes ideation through three lenses: market value, user experience, and technical feasibility. That helps avoid one-sided lists that are either too abstract or too implementation-heavy.
It is most useful when you have:
- a target segment,
- a problem or opportunity,
- and a desired outcome or business goal.
When this skill is a good fit
Choose brainstorm-ideas-new if you are trying to answer:
- What features could make this new product compelling?
- Which ideas deserve validation first?
- How might PM, design, and engineering think differently about the same opportunity?
Do not use it as a replacement for deep research, roadmap prioritization, or delivery planning. It is for idea generation, not final product strategy.
What to expect from the output
A good run should give you candidate feature ideas that are specific, varied, and grounded in the product context you supplied. The quality depends heavily on how clearly you describe the opportunity and constraints in your prompt.
How to Use brainstorm-ideas-new skill
Install and locate the skill
Install brainstorm-ideas-new from the phuryn/pm-skills collection with:
npx skills add phuryn/pm-skills --skill brainstorm-ideas-new
After install, open SKILL.md first. In this repository, there are no supporting scripts/, resources/, or references/ folders, so the core guidance lives in the skill file itself.
Give it a complete discovery brief
The brainstorm-ideas-new usage works best when your input includes enough context for the skill to reason about the opportunity. A strong prompt usually names:
- the product idea,
- target user segment,
- problem to solve,
- current alternatives,
- business goal,
- constraints such as platform, timeline, or scope.
A weak prompt like “brainstorm ideas for my app” will usually produce broad, low-signal output. A stronger prompt looks more like:
“Brainstorm feature ideas for a B2B onboarding product for small SaaS teams. The goal is to reduce time-to-value in the first 7 days. Focus on ideas that help PM, design, and engineering evaluate the opportunity for an MVP.”
Read the workflow in the right order
For this skill, start with SKILL.md and then follow any linked or neighboring docs if they exist in your local copy. Since the repo is light on support files, the main value is understanding the instruction flow:
- confirm the product concept and segment,
- generate ideas from three viewpoints,
- filter for relevance to initial discovery.
That sequence matters because it keeps the output anchored to validation, not random feature expansion.
Improve results with better input shape
The fastest way to improve brainstorm-ideas-new guide output is to add decision-relevant context, not more adjectives. Include market stage, whether the product is greenfield or adjacent to an existing product, and what “good” looks like for this brainstorm. If you already know your no-go zones, say so upfront.
brainstorm-ideas-new skill FAQ
Is brainstorm-ideas-new only for brand-new products?
Yes, primarily. The skill is tuned for initial discovery, not continuous iteration on an existing product. If you already have live users, usage data, and an active roadmap, a different discovery or prioritization skill will usually fit better.
How is this better than a normal prompt?
A normal prompt can ask for ideas, but brainstorm-ideas-new gives you a discovery-oriented structure: understand the opportunity first, then generate ideas from PM, Designer, and Engineer perspectives. That makes the output easier to compare and use in Strategic Planning.
Do I need product expertise to use it well?
No. Beginners can use it if they can describe the target user and problem clearly. The main limitation is not expertise; it is input quality. The more specific your segment and goal, the more actionable the ideas become.
When should I not use this skill?
Do not use it when you need:
- deep customer research synthesis,
- implementation planning,
- final prioritization,
- or a polished product requirements document.
This brainstorm-ideas-new skill FAQ is about early ideation, so it is strongest before the product direction is locked.
How to Improve brainstorm-ideas-new skill
Start with sharper opportunity framing
The biggest quality gain comes from defining the opportunity in one sentence before asking for ideas. State who the user is, what they struggle with, and why now matters. That helps the skill avoid generic feature lists and produce ideas tied to a real product bet.
Give explicit constraints and tradeoffs
If you want practical output, include constraints such as B2B vs B2C, mobile vs web, solo user vs team workflow, or speed vs depth. These constraints help the brainstorm stay realistic and improve the brainstorm-ideas-new install decision because the results will better reflect your actual build space.
Ask for ideas you can validate
The best next step after the first output is to ask which ideas are easiest to test, which are highest risk, and which require the least build effort. That turns raw ideation into a shortlist you can use for interviews, prototype tests, or internal review.
Iterate by narrowing the lens
If the first pass is too broad, rerun the skill with a narrower segment or a more explicit outcome. For example, switch from “new productivity app” to “new productivity app for freelance designers who need better client handoff.” Narrower inputs usually produce better strategic options and less noise.