From pm-product-discovery
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 this skill is triggered — by the user, by Claude, or both
Slash command
/pm-product-discovery:brainstorm-ideas-existingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five.
Multi-perspective ideation for continuous product discovery. Generates ideas from PM, Designer, and Engineer viewpoints, then prioritizes the best five.
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.
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.
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:
Prioritize the top 5 ideas across all perspectives based on:
For each prioritized idea, provide:
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.
npx claudepluginhub unixcrh/phuryn-pm-skills --plugin pm-product-discoveryProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.