Analyzes and prioritizes feature requests by theme, strategic alignment, impact, effort, and risk. Use for customer request reviews, backlog triaging, or prioritization.
From pm-product-discoverynpx claudepluginhub jupitermoney/pm-superic-skills --plugin pm-product-discoveryThis skill uses the workspace's default tool permissions.
Guides browser automation with Playwright, Puppeteer, Selenium for e2e testing and scraping. Teaches reliable selectors, auto-waits, isolation to fix flaky tests.
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.
Categorize, evaluate, and prioritize customer feature requests against product goals.
You are analyzing feature requests for $ARGUMENTS.
If the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.
Never allow customers to design solutions. Prioritize opportunities (problems), not features. Use Opportunity Score (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the prioritization-frameworks skill for full details and templates.
The user will describe their product goal and provide feature requests. Work through these steps:
Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
Categorize requests into themes: Group related requests together and name each theme.
Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
Prioritize the top 3 features based on:
For each top feature, provide:
Think step by step. Save as markdown or create a structured output document.