cmd-scope-sweep
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseScope Sweep
范围核查
Now that we've completed the core work and reviewed it, do a final pass to identify anything we missed or should address before considering this scope "done".
Please check for:
- Incomplete tasks: anything you planned to do but didn't get to
- Overlooked requirements: anything implied but not explicitly handled
- Missing questions: what I should have asked but didn't
- Hidden assumptions: any assumptions you made that could be wrong
- Edge cases: scenarios that could break or degrade the solution
- Failure modes: what happens when inputs are malformed, missing, hostile, or extreme
- Operational concerns: deployment, monitoring, logging, maintenance, rollback
- Security and abuse risks: permissions, misuse paths, data exposure
- Performance bottlenecks: scalability issues, worst-case behavior, cost traps
- Testing gaps: what still needs tests or validation
- User experience gaps: confusing flows, unclear outputs, poor defaults
- Integration risks: dependencies, external APIs, versioning, backward compatibility
- Future-proofing: what will become painful in 3-6 months if not handled now
Finally:
- What is the biggest risk remaining?
- If you were reviewing this as a third party, what would you criticize first?
- What would you improve if you had one more day?
我们已经完成核心工作并完成评审，接下来请做一次最终核查，在确认该范围「已完成」前，识别出所有我们遗漏的或需要处理的事项。
请核查以下内容：
- 未完成任务：你计划完成但尚未推进的所有事项
- 被忽略的需求：所有隐含但未被明确处理的需求
- 遗漏的问题：我本应提出但未提及的问题
- 隐含假设：你做出的所有可能存在错误的假设
- 边界场景：可能导致解决方案崩溃或性能下降的场景
- 故障模式：当输入出现格式错误、缺失、恶意或极端情况时会发生的问题
- 运维相关问题：部署、监控、日志、维护、回滚相关事项
- 安全与滥用风险：权限、滥用路径、数据暴露相关风险
- 性能瓶颈：可扩展性问题、最坏情况表现、成本陷阱
- 测试缺口：仍需要测试或验证的内容
- 用户体验缺口：流程令人困惑、输出不清晰、默认值不合理的问题
- 集成风险：依赖项、外部API、版本控制、向后兼容性相关风险
- 未来兼容性：如果现在不处理，3-6个月后会变得棘手的问题
最后：
- 剩余的最大风险是什么？
- 如果你以第三方身份评审该项目，你最先会批评什么内容？
- 如果多给你一天时间，你会优化什么内容？