agentsclimarketplace

Analyze feature requests

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

PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth.

Install
npx -y skills add phuryn/pm-skills --skill analyze-feature-requests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.2 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.