From pm-product-discovery
Brainstorms feature ideas for new products from PM, Designer, and Engineer perspectives. Prioritizes top ideas for initial discovery, startup ideation, or product validation.
npx claudepluginhub lamngit1995/phuryn-pm-skills --plugin pm-product-discoveryThis skill uses the workspace's default tool permissions.
Provides checklists to review code for functionality, quality, security, performance, tests, and maintainability. Use for PRs, audits, team standards, and developer training.
Enforces A/B test setup with gates for hypothesis locking, metrics definition, sample size calculation, assumptions checks, and execution readiness before implementation.
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.
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.