Skip to content

phuryn/pm-skills / pm-product-discovery/skills/analyze-feature-requests

analyze-feature-requests

Verified

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.

Analyze Feature Requests

Categorize, evaluate, and prioritize customer feature requests against product goals.

Context

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.

Domain Context

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.

Instructions

The user will describe their product goal and provide feature requests. Work through these steps:

  1. Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.

  2. Categorize requests into themes: Group related requests together and name each theme.

  3. Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.

  4. Prioritize the top 3 features based on:

    • Impact: Customer value and number of users affected
    • Effort: Development and design resources required
    • Risk: Technical and market uncertainty
    • Strategic alignment: Fit with product vision and goals
  5. For each top feature, provide:

    • Rationale (customer needs, strategic alignment)
    • Alternative solutions worth considering
    • High-risk assumptions
    • How to test those assumptions with minimal effort

Think step by step. Save as markdown or create a structured output document.


Further Reading

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall