problem-brief
发布并维护问题简报:一页面向操作者的发现、待决事项和问题,每项包含问题、证据和建议的解决途径,以 JSON 保存并记录每项裁定,确保同一问题不会被重复询问。默认情况下,无需被要求,只要工作中出现需要操作者决定的事项(有多个解决途径的发现、风险、开放问题、选项之间的选择),即使任务进行中、即使操作者只要求调查,也应使用。也适用于被要求构建、发布、刷新或更新简报、发现报告、开放问题或决策页面时;当操作者在聊天中或页面评论中对简报内容作出回答、裁定或评论时;当问题原本会通过 AskUserQuestion 发出时;以及当简报工作完成需要归档时。不适用于没有待决事项的进度、状态或完成报告,不适用于运行 chorus 评审,也不适用于将 chorus 记录转换为共享 schema。
机器翻译查看英文原文
Publishes and maintains a problem brief: a page of findings, open decisions and questions for the operator, each with the problem, evidence and a recommended way out, kept as JSON that records every ruling so nothing is asked twice. Use by default, without being asked, whenever work turns up something the operator must decide (a finding with more than one way out, a risk, an open question, a choice between options), even mid-task and even when the operator only asked for an investigation. Also use when asked to build, publish, refresh or update a brief, findings report, open-questions or decisions page; when the operator answers, rules on or comments on anything a brief holds, in chat or in a comment on the page; when questions would otherwise go out through AskUserQuestion; and when retiring a brief whose work is done. Not for a progress, status or completion report with nothing to decide, for running a chorus review, or for converting chorus records to the shared schema.
适用对象:对象待分类。自动收录 · 待核查。
在 Claude Code 中使用
该组合的专门教程待补充,尚未核实适配。
准备条件
- 本条仅收录原作者的技能元数据;请阅读完整说明,确认依赖、许可与使用条件。
选择已有说明的 AI 工具,或在页面加载后保存待办及提出教程请求。
查看原作者说明 ↗