brainstorm-ideas-existing
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
- Installs
- 3K
- Last 24h
- +8
- Trending rank
- #9484
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-ideas-existing- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads brainstorm-ideas-existing automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Brainstorm Product Ideas (Existing Product)
Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five.
Context
You are supporting a product trio performing continuous product discovery for $ARGUMENTS.
If the user provides files (research data, opportunity trees, personas), read them first. If they mention a product URL, use web search to understand the product.
Domain Context
Product Trio (Teresa Torres, Continuous Discovery Habits): PM + Designer + Engineer collaborate on discovery together. "Best ideas often come from engineers." Discovery is not linear — loop back if experiments fail. Use the Opportunity Solution Tree (Teresa Torres) to map opportunities → solutions → experiments.
Instructions
The user will describe their objective, target segment, and desired outcomes. Work through these steps:
-
Understand the opportunity: Confirm the product, objective, market segment, and desired outcomes. Ask for clarification if anything is ambiguous.
-
Ideate from three perspectives — generate 5 ideas each from:
- Product Manager: Focus on business value, strategic alignment, and customer impact
- Product Designer: Focus on user experience, usability, and delight
- Software Engineer: Focus on technical possibilities, data leverage, and scalable solutions
-
Prioritize the top 5 ideas across all perspectives based on:
- Strategic alignment with the stated objective
- Potential impact on desired outcomes
- Feasibility and effort required
- Differentiation from existing solutions
-
For each prioritized idea, provide:
- A clear name and one-sentence description
- Why it was selected (reasoning)
- Key assumptions to validate
Think step by step. Present ideas in a clear, structured format.
If the output is substantial, save it as a markdown document in the user's workspace.
Further Reading
FAQ
What does the brainstorm-ideas-existing skill do?
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
How do I install brainstorm-ideas-existing?
Run npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-ideas-existing in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/brainstorm-ideas-existing/ (personal) or .claude/skills/brainstorm-ideas-existing/ (project).
Which AI agents can use brainstorm-ideas-existing?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is brainstorm-ideas-existing safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains brainstorm-ideas-existing?
It is published by phuryn in phuryn/pm-skills. It has 3,046 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.