Project Retrospective Template Checklist: quick fix, steps, and deep guide

Q: Project Retrospective Template Checklist

Treat this as a AI tools checklist issue. Confirm the environment, inputs, permissions, logs, and delivery boundary, then use the linked deep guide for the full checklist.

What is the problem?

项目复盘写完后，要检查是否区分事实和判断、是否保留验证证据、是否记录范围变化、是否脱敏，以及是否写出下次可执行改进。

Quick solution

Treat this as a AI tools checklist issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.

Read the deep guide

Detailed steps

是否写清项目目标。
是否区分事实、判断和情绪。
是否列出完成和未完成。
是否有截图、命令、链接或客户确认。
是否记录范围变化。
是否写明问题原因。

Commands or code

复盘检查表

目标清楚：是 / 否
事实完整：是 / 否
证据齐全：是 / 否
问题原因：已写 / 未写
下次动作：具体 / 模糊
敏感信息：已检查 / 待处理
是否可公开：是 / 否
明日待办：

Risk notes

Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.