analyze-feature-requests
phuryn/pm-skills
根据战略契合度、影响、工作量和风险分析,结合产品目标对客户的功能需求进行分类、评估和优先级排序。
...展开全部分析功能需求
根据产品目标对客户的功能需求进行分类、评估和优先级排序。
背景
您正在分析针对$ARGUMENTS 的功能需求。
如果用户提供了文件(电子表格、CSV 文件或包含功能需求的文档),请直接阅读并分析这些文件。如果数据采用结构化格式,请考虑创建一个汇总表。
领域背景
切勿让客户设计解决方案。应优先处理机会(问题),而非功能。使用“机会评分”(Dan Olsen 提出)来评估客户报告的问题:机会评分 = 重要性 × (1 − 满意度),并归一化为 0–1 之间。有关完整细节和模板,请参阅“优先级框架”技能。
操作指南
用户将描述其产品目标并提出功能需求。请按照以下步骤操作:
理解目标:确认产品目标及预期成果,这些将指导优先级排序。
将需求分类为主题:将相关需求归类,并为每个主题命名。
评估战略契合度:针对每个主题,评估其与既定目标的契合程度。
根据以下标准确定前3项功能的优先级:
- 影响:客户价值及受影响的用户数量
- 工作量:所需的开发和设计资源
- 风险:技术和市场的不确定性
- 战略契合度:与产品愿景和目标的契合程度
针对每项优先级最高的功能,请提供:
- 理由(客户需求、战略契合度)
- 值得考虑的替代方案
- 高风险假设
- 如何以最小的投入验证这些假设
请分步思考。保存为 Markdown 格式或生成结构化的输出文档。
延伸阅读
- 卡诺模型:如何在不沦为“功能工厂”的情况下让客户满意
- 持续产品探索大师班(CPDM)(视频课程)
---
name: analyze-feature-requests
description: Categorize, evaluate, and prioritize customer feature requests against product goals using strategic alignment, impact, effort, and risk analysis.
---
## 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
- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)





首页
