brainstorm-ideas-existing
This skill facilitates structured ideation for existing products by generating and prioritizing feature ideas from three distinct perspectives: Product Manager, Designer, and Engineer. Use it when a product team needs to brainstorm solutions for identified opportunities, explore new feature directions, or conduct collaborative discovery sessions where cross-functional viewpoints are essential for generating comprehensive, feasible concepts.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/brainstorm-ideas-existing && cp -r /tmp/brainstorm-ideas-existing/pm-product-discovery/skills/brainstorm-ideas-existing ~/.claude/skills/brainstorm-ideas-existingSKILL.md
## 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: 1. **Understand the opportunity**: Confirm the product, objective, market segment, and desired outcomes. Ask for clarification if anything is ambiguous. 2. **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 3. **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 4. **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 - [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery) - [Product Trio: Beyond the Obvious](https://www.productcompass.pm/p/product-trio) - [The Extended Opportunity Solution Tree](https://www.productcompass.pm/p/the-extended-opportunity-solution-tree) - [Product Model First Principles: Product Discovery, Product Delivery, and Product Culture In Depth](https://www.productcompass.pm/p/product-model-first-principles-discovery-deliver) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze 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.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.