先看看示例
作者提供的示例，实际效果取决于你的输入和使用工具。
输入
反馈：希望加文件夹；搜索找不到以前的资料；想给资料打标签。目标：帮助用户找回资料。
输出
编辑示例 · 未运行
主题：找回已有资料。
原请求映射：文件夹与标签是组织方案；搜索反馈指向检索失败。
优先验证：请用户演示最近一次找不到资料的过程，判断主要障碍是命名、分类还是搜索。
暂不承诺：同时开发文件夹和标签。
缺口：影响人数、频率与搜索失败原因未知。
方法说明
--- 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: 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)