analyze-feature-requests
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAnalyze 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.
你正在为**$ARGUMENTS**分析功能请求。
如果用户提供了包含功能请求的文件(如电子表格、CSV或文档),请直接读取并分析。若数据为结构化格式,可考虑创建汇总表格。
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 skill for full details and templates.
prioritization-frameworks切勿让客户主导解决方案设计。应优先关注机会(问题),而非具体功能。使用Opportunity Score(Dan Olsen提出)评估客户反馈的问题:Opportunity Score = 重要性 × (1 − 满意度),结果归一化至0–1区间。如需完整细节和模板,请查看技能文档。
prioritization-frameworksInstructions
操作步骤
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.
用户会描述其产品目标并提供功能请求,请按以下步骤操作:
-
明确目标:确认将作为优先级排序依据的产品目标和预期成果。
-
按主题分类请求:将相关请求分组,并为每个主题命名。
-
评估战略契合度:针对每个主题,评估其与既定目标的契合程度。
-
选出优先级最高的3项功能,评估维度包括:
- 影响范围:客户价值及受影响用户数量
- 实施成本:所需的开发和设计资源
- 风险:技术和市场不确定性
- 战略契合度:与产品愿景和目标的匹配度
-
针对每个高优先级功能,提供以下内容:
- 优先级理由(客户需求、战略契合度)
- 值得考虑的替代方案
- 高风险假设
- 如何以最小成本验证这些假设
请逐步推进工作。最终结果保存为Markdown格式或结构化输出文档。