analyze-feature-requests
GitHub分析并优先排序功能请求，基于主题、战略一致性、影响、风险和机会得分进行优先级评估。适用于客户反馈审查、积压工作分类及决策制定。
Trigger Scenarios
Install
npx skills add phuryn/pm-skills --skill analyze-feature-requests -g -y
SKILL.md
Frontmatter
{
"name": "analyze-feature-requests",
"description": "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:
-
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:
- 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
-
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
Version History
- 18468a9 Current 2026-07-25 10:32
