减少策划分析与正文重复
Project CI / AI game creator shell Rust shard 1/4 (pull_request) Failing after 2m6s
Project CI / AI game creator shell Rust shard 2/4 (pull_request) Failing after 2m41s
Project CI / AI game creator shell Rust smoke (pull_request) Failing after 2m13s
Project CI / AI game creator shell Rust shard 4/4 (pull_request) Failing after 2m34s
Project CI / AI game creator shell Rust shard 3/4 (pull_request) Failing after 2m37s
Project CI / AI game creator shell Rust crates (pull_request) Successful in 2m52s
Project CI / Native shell tests (pull_request) Failing after 4m28s
Project CI / Frontend tests (pull_request) Successful in 4m41s
Project CI / Repository checks (pull_request) Successful in 3m28s
Project CI / Backend tests (pull_request) Successful in 6m39s
Project CI / AI game creator shell web tests (pull_request) Successful in 2m18s

要求分析优先保留决策摘要

要求形成结论后直接写入正式产物并检查
This commit is contained in:
2026-09-15 16:23:47 +08:00
parent 319dfec9e4
commit 49a10d820f
@@ -3,6 +3,8 @@
优先完成能够依据已有信息推进的工作,不要为每个设计空白都询问用户。局部、可逆的问题可以先提出合理方案并标为暂定。会影响当前阶段范围、关键规则、下游实现或其他重要方向,且必须由用户决定的问题,应先通过纯文本或问询工具询问,等待用户回答。决定稳定后,再更新受影响的正式产物和必要的过程记录;不要带着这类未决问题提交阶段审批。
分析阶段优先记录当前目标、上层约束、候选方案、取舍、用户已确认或 Agent 暂定的边界,以及必须检查的验收项。除非用户明确要求展开讨论,不要先在回复中逐节起草与正式文档重复的长篇正文;形成结论后直接写入正式产物,再进行一次必要的一致性检查。文件操作前只需说明简短计划、目标文件和主要变化。
正式策划文档在文档头部写明版本标记,例如“版本:v1”。由你自行维护版本号:只有整体修订、阶段性定稿或用户意见造成实质内容变化时才递增;错别字、措辞润色、单个局部修改和小范围补充不单独递增。
阶段审批是每个阶段的最终检查,表示本阶段产物已经完成,无未决内容,交给用户做最终检阅,不承担问询功能。提交前,解决所有影响本阶段完成的关键问题,或明确说明它们不阻塞本阶段交付,并更新相关产物。可以保留不阻塞当前阶段的后续事项和待原型验证项。