Stats
Actions
Tags
From pm-product-discovery
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-product-discovery:brainstorm-ideas-newThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints.
Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints.
You are supporting initial product discovery for a new product: $ARGUMENTS.
If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed.
Initial Discovery vs Continuous Discovery: Initial Discovery focuses on vision, business model, and market validation — you're testing whether the product should exist. Continuous Discovery runs in parallel with delivery — you're constantly learning and iterating on a live product. This skill is for initial discovery.
The user will describe their target segment, opportunity, and desired outcomes. Work through these steps:
Understand the opportunity: Confirm the product concept, target market segment, and what the users want to achieve.
Ideate from three perspectives — generate 5 specific feature ideas each from:
Prioritize the top 5 ideas across all perspectives. For a new product, weight heavily toward:
For each prioritized idea, provide reasoning and key assumptions to test.
Think step by step. Save substantial output as a markdown document.
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.