首頁
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)
所有檔案
1 個檔案安裝 analyze-feature-requests
請下載並將技能檔案解壓縮至您的 .claude/skills/ 目錄中。
下載 ZIP複製儲存庫並將技能檔案複製到您的專案中。
git clone https://github.com/phuryn/pm-skills/tree/main/pm-product-discovery/skills/analyze-feature-requests # Copy SKILL.md to your .claude/skills/ directory
複製
