归档反馈处理 · Feedback Archiver

它解决什么问题

用户反馈散在客服工单、评论区和聊天记录里,同一问题被反复提,重要问题却没人跟进,最后「收集了一堆,处理了没有」都说不清。这个技能把零散反馈归档成一张可执行的处理台账:每条反馈都有分级、责任人与闭环期限,重复项自动合并,谁在什么时候该做什么一目了然。

这个技能做什么

围绕反馈处理提供结构化归档能力:先澄清反馈来源、产品范围与处理团队,再把原始反馈清洗为「问题-影响-建议-优先级」的标准条目,合并重复项,输出处理台账(分级/责任归属/闭环期限)与跟进节奏建议。默认中文输出,不确定的信息标注「待确认」。

为什么比裸提示词强

• 内置分级规则:P0 阻断/P1 高频痛点/P2 优化建议,不再凭感觉排期
• 重复项自动合并:同一问题的多条反馈归并成一条,附原始条数
• 每条都有闭环期限与责任人,反馈不会「收集完就消失」
• 结论先行:先给「本周最该处理的三件事」,再给完整台账

典型用例

• 客服团队把一周工单反馈归档成产品周会材料
• 新版本上线后,把社区评论归档成修复优先级清单
• 把多个渠道的反馈合并成一张跨部门处理台账
• 定期复盘哪些反馈已闭环、哪些长期搁置

局限

技能基于你提供的反馈文本归档,不接入工单系统自动抓取;涉及用户隐私的内容请在归档前脱敏。

English · 英文介绍

The problem

User feedback is scattered in customer service tickets, comment areas and chat records. The same question is raised repeatedly, but no one follows up on important issues. In the end, it is unclear whether "a bunch of them have been collected and processed." This skill archives scattered feedback into an executable processing ledger: each feedback has a rating, responsible person and closed-loop deadline, duplicate items are automatically merged, and it is clear who should do what when.

What it does

Provide structured archiving capabilities around feedback processing: first clarify the source of feedback, product scope and processing team, then clean the original feedback into standard items of "problem-impact-suggestion-priority", merge duplicate items, output processing ledger (grading/responsibility/closed-loop deadline) and follow-up rhythm suggestions. The default output is Chinese, and uncertain information is marked "to be confirmed".

Why is it better than naked prompt words?

• Built-in grading rules: P0 blocking/P1 high-frequency pain points/P2 optimization suggestions, no longer scheduling based on feeling
• Duplicates are automatically merged: multiple feedbacks on the same issue are merged into one, with the original number attached.
• Each item has a closed-loop deadline and responsible person, and feedback will not “disappear as soon as it is collected.”
• Conclusion first: first give "the three most important things to deal with this week", and then give the complete account

Typical use cases

• The customer service team files the weekly work order feedback into weekly product meeting materials
• After the new version is launched, community comments are archived into a fix priority list
• Consolidate feedback from multiple channels into one cross-department processing ledger
• Regularly review which feedback has been closed and which has been shelved for a long time

Limitations

Skills are archived based on the feedback text you provide, and are automatically captured without being connected to the work order system; please desensitize content involving user privacy before archiving.