brainstorm-ideas-existing
by phurynbrainstorm-ideas-existing is a product discovery skill for generating ideas around an existing product using PM, Designer, and Engineer viewpoints. It helps you explore opportunities, narrow promising directions, and prioritize concepts for Product Management workflows and trio-based discovery.
This skill scores 74/100 and is worth listing: it gives directory users a clear, specific use case for brainstorming ideas for an existing product, with enough workflow structure to be more actionable than a generic prompt. It is still somewhat limited by the lack of supporting files or deeper execution aids, so users should expect a solid but lightweight install rather than a fully instrumented workflow.
- Clear trigger and use case: brainstorm product ideas for an existing product, especially for product trio discovery
- Multi-perspective workflow: explicitly generates ideas from PM, Designer, and Engineer viewpoints and prioritizes the best five
- Operational context is reasonably explicit: asks to confirm product, objective, segment, outcomes, and to read provided files or use web search when relevant
- No support files, scripts, or references, so users get little auxiliary guidance beyond the SKILL.md text
- Workflow appears concise rather than exhaustive, which may limit handling of complex or highly ambiguous discovery sessions
Overview of brainstorm-ideas-existing skill
brainstorm-ideas-existing is a product discovery skill for generating new ideas around an existing product, not for inventing from scratch. It helps a product trio think through an opportunity from PM, Designer, and Engineer perspectives, then narrow the output to the most promising directions. Use it when you already have a product, a target segment, and a problem to solve, and you want more structured ideation than a generic prompt can provide.
What this skill is best for
The brainstorm-ideas-existing skill is strongest when you need fresh feature ideas, solution alternatives for a known opportunity, or a better starting set of hypotheses for product discovery. It is especially useful for Product Management work where the goal is to connect customer pain, business value, and implementation reality before committing to a roadmap direction.
What makes it different
Unlike a loose brainstorming prompt, this skill explicitly uses multiple viewpoints and prioritization. That matters because it reduces one-dimensional ideas and helps surface options that are actually worth testing. It also encourages a discovery loop, which is useful when your first pass is not good enough or your evidence is incomplete.
When it is a good fit
Choose brainstorm-ideas-existing if you can answer three things: what product you are working on, what opportunity or problem you are exploring, and who the ideas should serve. If you only need generic creativity, this is probably more process than you need. If you need ideas that are more grounded in product strategy and execution constraints, it is a better fit.
How to Use brainstorm-ideas-existing skill
Install and locate the skill
Install with npx skills add phuryn/pm-skills --skill brainstorm-ideas-existing. For the brainstorm-ideas-existing install decision, the important point is that this repo is lean: there are no helper scripts or support folders to inspect, so SKILL.md is the main source of truth. Start there, then verify the frontmatter and read the skill body before adapting it to your workflow.
Give the skill the right input
The brainstorm-ideas-existing usage pattern works best when your prompt includes a product name, a specific opportunity, the audience, and the outcome you want. Good input sounds like: “Brainstorm ideas for our existing fitness app to improve retention for new users who churn in week one.” Weak input sounds like: “Give me ideas for my product.” The first gives the skill enough context to produce useful ideas; the second forces it to guess.
Use a trio-style prompt
The skill is designed to think like a PM, Designer, and Engineer, so frame the request around decision-making, not just ideation. A practical brainstorm-ideas-existing guide is to ask for ideas by viewpoint, then request a short prioritization pass. For example: “Generate 5 ideas from PM, 5 from Design, 5 from Engineering, then rank the top 5 by impact, feasibility, and confidence.” That structure matches the skill’s workflow and makes the output easier to use in workshops or planning.
Read the source files first
For this repository, SKILL.md is the main file to review first because there are no README.md, rules/, resources/, or scripts to extend the workflow. If you are adapting brainstorm-ideas-existing for your own organization, the most important step is not copying the wording but preserving the sequence: confirm context, ideate from multiple perspectives, then prioritize. That order is what keeps the output tied to a real product problem.
brainstorm-ideas-existing skill FAQ
Is brainstorm-ideas-existing only for Product Management?
No. The brainstorm-ideas-existing skill is useful for Product Management, but it is intentionally cross-functional. It works best when PM, Design, and Engineering concerns are all relevant to the decision, especially when you want ideas that are both desirable and buildable.
How is this different from a normal prompt?
A normal prompt may produce ideas, but brainstorm-ideas-existing adds structure: it asks for context, separates viewpoints, and pushes toward prioritization. That usually gives you more usable output and fewer generic suggestions, especially when the opportunity is complex or the team needs a shared starting point.
Is it beginner-friendly?
Yes, if you already know the product and the problem. You do not need discovery expertise to use the skill, but you do need to provide enough context for it to work. Beginners get better results when they describe the product, the user segment, and the business goal in one short paragraph before asking for ideas.
When should I not use it?
Do not use brainstorm-ideas-existing when the problem is undefined, the product is unknown, or you only want a quick list of random concepts. It is also not the right choice if you need deep research synthesis, UX copy, or implementation specs. Its value is upstream of those tasks: turning a known opportunity into better product options.
How to Improve brainstorm-ideas-existing skill
Start with sharper constraints
The best brainstorm-ideas-existing results come from clear boundaries: target segment, product stage, metric, and known pain point. If you say “increase activation for self-serve SMB admins in the first 7 days,” you will get better ideas than if you say “improve onboarding.” Constraints help the skill trade breadth for relevance.
Ask for output you can evaluate
Do not stop at idea generation. Ask the skill to include why each idea matters, what perspective produced it, and how it should be judged. For example: “For each idea, note the intended user value, expected business impact, and main implementation risk.” That makes the brainstorm-ideas-existing skill more decision-ready and easier to discuss with a product trio.
Use iteration after the first pass
The first output is usually a starting point, not the final answer. If the ideas feel too broad, narrow the audience or outcome. If they feel too safe, ask for bolder options or adjacent opportunities. If they feel too expensive, ask for lower-effort variants. Iterating this way is how the brainstorm-ideas-existing skill becomes useful in real product discovery instead of staying at the level of a workshop exercise.
Improve the prompt with evidence
Add research notes, customer quotes, funnel data, or the current product limitation when you have them. The skill is designed to work with opportunity context, so evidence helps it avoid generic brainstorming. Strong inputs are the fastest way to improve brainstorm-ideas-existing usage and get ideas that can move into experiments, not just discussion.