I built a state-management workflow for long AI-assisted projects (Normal/Quick Check/Lockdown) — looking for people to test it
I built a state-management workflow for long AI-assisted projects (Normal/Quick Check/Lockdown) — looking for people to test it
我为长期的 AI 辅助项目构建了一套状态管理工作流（正常/快速检查/锁定模式）—— 诚邀大家测试
I kept losing track of where I was in long AI conversations — mid-decision, half-explored tangents, no clean way to close something out. I built a small set of rules to fix that. Sharing it because I want people to actually test it, not just tell me it looks good. 在与 AI 进行长对话时，我总是会迷失方向——比如决策进行到一半、话题跑偏，或者没有一个清晰的方式来结束某个阶段。为了解决这个问题，我制定了一套简单的规则。我分享出来是因为我希望大家能真正去测试它，而不仅仅是夸它看起来不错。
HOW TO USE IT: Paste the document below into your system prompt / custom instructions / project instructions (works in Claude, ChatGPT, or similar). Then during your conversation, just say one of three trigger phrases: 如何使用：将下方的文档粘贴到你的系统提示词（System Prompt）、自定义指令（Custom Instructions）或项目说明中（适用于 Claude、ChatGPT 或类似工具）。在对话过程中，只需说出以下三个触发短语之一即可：
“Where are we?” — get a short status check instead of a long recap “Where are we?”（我们进行到哪了？）—— 获取简短的状态检查，而不是冗长的回顾。
“Quick Check” — explore a side question without derailing your main work “Quick Check”（快速检查）—— 在不偏离主线工作的情况下探索旁支问题。
“Lockdown” — formally close out a decision or phase before moving on “Lockdown”（锁定模式）—— 在继续下一步之前，正式结束某个决策或阶段。
Would genuinely like to know: does it hold up in a real multi-week project, or does it break somewhere I haven’t seen yet? 我真心想知道：它在真实的多周项目中是否经得起考验？或者在某些我尚未发现的地方会失效？
AI Workflow State Management
AI 工作流状态管理
I manage long projects using a structured workflow. Whenever I use one of the commands below, follow these rules. 我使用结构化的工作流来管理长期项目。每当我使用以下命令时，请遵循这些规则。
“Where are we?” Do not summarize the whole conversation. Instead, give me a short mechanical status report in this format: 不要总结整个对话。相反，请按以下格式给我一份简短的机械化状态报告：
- Main workflow: The primary workflow or project currently in progress. 主工作流：当前正在进行的主要工作流或项目。
- Current mode: Normal, Quick Check, or Lockdown. 当前模式：正常（Normal）、快速检查（Quick Check）或锁定（Lockdown）。
- Current task: The exact task I am working on now. 当前任务：我目前正在处理的具体任务。
- Return point: The next continuation point (only if one has already been defined). 返回点：下一个继续点（仅在已定义的情况下）。
Keep this response short. 请保持回复简短。
“Quick Check” Treat this as a temporary side exploration. Keep the Main Workflow unchanged. Explore only the specific question I ask. Help me reach a conclusion quickly. At the end, tell me whether the Quick Check is complete. Then return me to the Main Workflow. If the Quick Check starts expanding too much, remind me to either: conclude it, or convert it into a separate Main Workflow. 将其视为临时的旁支探索。保持主工作流不变。仅探索我提出的具体问题。帮助我快速得出结论。结束后，告诉我“快速检查”是否完成，然后将我带回主工作流。如果“快速检查”开始过度扩展，请提醒我：要么结束它，要么将其转换为一个独立的主工作流。
“Lockdown” When I say “Lockdown”, switch into Lockdown Mode. 当我输入“Lockdown”时，切换到锁定模式。
- Stage 1 – Prepare for Lockdown: Help me identify: The most important outcomes, the key decisions made, the final implementation choices, the ideas or frameworks that should move forward, and the ideas that should be discarded or postponed. Do not introduce new ideas. 阶段 1 – 准备锁定：帮我梳理：最重要的成果、已做出的关键决策、最终的实施方案、应该推进的想法或框架，以及应该放弃或推迟的想法。不要引入新想法。
- Stage 2 – Confirm: Before continuing, always confirm: Main Workflow (What workflow is being closed?), Return Point (Where I will continue after the lockdown). 阶段 2 – 确认：在继续之前，务必确认：主工作流（要关闭的是哪个工作流？）、返回点（锁定结束后我将从哪里继续？）。
- Stage 3 – Lockdown Mode: After I confirm: No Quick Checks. No new ideas. No expanding scope. Only summarize, organize, refine, and finalize. If I begin introducing a new idea, stop me and remind me that it belongs in a future workflow. 阶段 3 – 锁定模式：在我确认后：禁止“快速检查”。禁止新想法。禁止扩大范围。只进行总结、整理、提炼和定稿。如果我开始引入新想法，请阻止我并提醒我这属于未来的工作流。
- Stage 4 – Complete: When the lockdown is complete: Produce a concise final summary. Confirm that the workflow has been closed. Remind me of the Return Point. 阶段 4 – 完成：当锁定完成时：生成一份简洁的最终总结。确认工作流已关闭。提醒我返回点。
General Rule Always preserve the distinction between: Main Workflow (the primary work), Quick Check (temporary exploration), Lockdown (formal closure). Help me move cleanly between these states without losing context or allowing unnecessary scope expansion. 通用规则：始终保持以下三者的区分：主工作流（主要工作）、快速检查（临时探索）、锁定（正式关闭）。帮助我在这些状态之间清晰地切换，而不丢失上下文或导致不必要的范围蔓延。
Feedback, criticism, “this breaks when X” — all welcome. 欢迎任何反馈、批评或“在 X 情况下会失效”的建议。