Brainstorm ideas existing skill
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints.
by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗
npx degit phuryn/pm-skills/pm-product-discovery/skills/brainstorm-ideas-existing#main ~/.claude/skills/brainstorm-ideas-existingChecked ·commit main
Files of Brainstorm ideas existing
Show the full text55 lines
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
| 1 | |
| 2 | name brainstorm-ideas-existing |
| 3 | description "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." |
| 4 | |
| 5 | |
| 6 | ## Brainstorm Product Ideas (Existing Product) |
| 7 | |
| 8 | Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five. |
| 9 | |
| 10 | ### Context |
| 11 | |
| 12 | You are supporting a product trio performing continuous product discovery for **$ARGUMENTS**. |
| 13 | |
| 14 | 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. |
| 15 | |
| 16 | ### Domain Context |
| 17 | |
| 18 | **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. |
| 19 | |
| 20 | ### Instructions |
| 21 | |
| 22 | The user will describe their objective, target segment, and desired outcomes. Work through these steps: |
| 23 | |
| 24 | **Understand the opportunity**: Confirm the product, objective, market segment, and desired outcomes. Ask for clarification if anything is ambiguous. |
| 25 | |
| 26 | **Ideate from three perspectives** — generate 5 ideas each from: |
| 27 | **Product Manager**: Focus on business value, strategic alignment, and customer impact |
| 28 | **Product Designer**: Focus on user experience, usability, and delight |
| 29 | **Software Engineer**: Focus on technical possibilities, data leverage, and scalable solutions |
| 30 | |
| 31 | **Prioritize the top 5 ideas** across all perspectives based on: |
| 32 | Strategic alignment with the stated objective |
| 33 | Potential impact on desired outcomes |
| 34 | Feasibility and effort required |
| 35 | Differentiation from existing solutions |
| 36 | |
| 37 | **For each prioritized idea**, provide: |
| 38 | A clear name and one-sentence description |
| 39 | Why it was selected (reasoning) |
| 40 | Key assumptions to validate |
| 41 | |
| 42 | Think step by step. Present ideas in a clear, structured format. |
| 43 | |
| 44 | If the output is substantial, save it as a markdown document in the user's workspace. |
| 45 | |
| 46 | |
| 47 | |
| 48 | ### Further Reading |
| 49 | |
| 50 | [What Is Product Discovery? The Ultimate Guide Step-by-Step] |
| 51 | [Product Trio: Beyond the Obvious] |
| 52 | [The Extended Opportunity Solution Tree] |
| 53 | [Product Model First Principles: Product Discovery, Product Delivery, and Product Culture In Depth] |
| 54 | [Continuous Product Discovery Masterclass (CPDM)] (video course) |
| 55 |
Discussion
Alternatives
Academy guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Analyze feature requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Advocacy program designerUse when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规Act as a product managerGuides the AI to act as a product manager, assisting in writing product requirement documents and addressing product-related queries.Browse more free Claude skills or everything in Product.