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)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
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.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
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.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.