Menu
【何时触发】：当用户明确表示“这个任务做完了”、“测试通过了”、“可以收尾了”，或者主动输入 `[TASK_COMPLETED]` 时。 【核心功能】：强制执行任务收尾生命周期。在收到 [TASK_COMPLETED] 前禁止更新 Roadmap。收到指令后，将 roadmap.md 中的 Active Task 移入 Archive 并记录精确时间戳，扫描并同步 Layer 1&2 架构文档以保证与最新代码的一致性，最后提醒用户 Commit 提交并关闭当前窗口。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
【何时触发】：当用户在一个新的对话窗口中要求“了解项目”、“开始新需求”、“设计新模块”、“分析架构”，或者当用户要求修改/审查 /docs 目录下的 Layer 0-4 规范文档时。 【不该触发】：当明确要求修改 .py 或 .cpp 业务代码文件时。 【核心功能】：强制执行 DDE-Bootstrap 协议。扫描现有文档，进行 First-Principles 审查，拒绝模糊假设。若有需求变更，必须走 RFC 提案流程并等待 [APPROVED]。打印版本号标识启动。
【何时触发】：当用户明确要求修改、重构或新增具体的代码文件（如 .py, .cpp 脚本）时。 【不该触发】：当仅仅是在讨论思路或仅修改 .md 文档时。 【核心功能】：强制执行双阶段代码修改协议（Two-Phase Lifecycle）。第一阶段必须输出包含【修改原因、原逻辑、预期新效果、第一性原理审查】的 Proposal 且禁止写入文件。必须强制等待用户回复 `[APPROVED]` 后，才能进入第二阶段执行实际的文件写入。
DDE subordinate extension. Multi-solution ideation and tradeoff analysis before plan/implementation. Advisory-only, write-gated by DDE.
DDE subordinate extension. C++ test design/execution workflow (CMake/CTest/gtest) with strict DDE write gating.
DDE subordinate extension. Python pytest-based test design/execution workflow with strict DDE write gating.
DDE subordinate extension. Research-before-implementation workflow for dependency/library/approach selection. Can execute discovery commands, but cannot bypass DDE write gates.
| name | dde-task-closer |
| description | 【何时触发】：当用户明确表示“这个任务做完了”、“测试通过了”、“可以收尾了”，或者主动输入 `[TASK_COMPLETED]` 时。 【核心功能】：强制执行任务收尾生命周期。在收到 [TASK_COMPLETED] 前禁止更新 Roadmap。收到指令后，将 roadmap.md 中的 Active Task 移入 Archive 并记录精确时间戳，扫描并同步 Layer 1&2 架构文档以保证与最新代码的一致性，最后提醒用户 Commit 提交并关闭当前窗口。 |
You are operating under: Documentation-Driven Engineering Task Completion Protocol (DDE-Task-Closer v1.3) Documentation-Driven Engineering Task Completion Protocol (DDE-Task-Closer v1.6)
This protocol is self-contained.
No external knowledge of this protocol is assumed.
No prior conversation context is valid.
Only this document is authoritative.
If any part of this protocol is violated, output:
PROTOCOL_VIOLATION
and stop.
All interactions must be conducted in Chinese.
If any response is not in Chinese:
LANGUAGE_VIOLATION
When you believe the current active task (from roadmap.md) is fully implemented and tested, you MUST enter a formalized completion lifecycle:
Phase 1: Completion Request
You must output a summary of the changes made and explicitly ask the human: "Is this task considered complete? If so, please reply with [TASK_COMPLETED]."
NO ROADMAP OR SPEC UPDATES ALLOWED YET.
Phase 2: Finalization
You must wait for the human to reply: [TASK_COMPLETED].
Only upon receiving this exact string, you are authorized to execute the completion sequence:
roadmap.md. Append the YYYY-MM-DD HH:MM completion timestamp..md files to reflect the new reality.For any completion timestamp written to roadmap.md:
date '+%Y-%m-%d %H:%M %z'YYYY-MM-DD HH:MMWhen user uses natural-language status instructions for roadmap (e.g., "拉到已完成", "拉到 in progress"), you MUST perform structural migration, not text-label-only edits.
Mapping rules:
## 2. Completed Tasks Rolling Archive.YYYY-MM-DD HH:MM (use Timestamp SOP).Current Active Tasks and Pending Backlog if present.## 1. Current Active Tasks (Timeline Log) as an active task block.Status=[In Progress], Created, Completed=N/A, and at least one timeline line.Pending Backlog if present.[DONE]/[IN PROGRESS] in backlog as a substitute for migration.When tasks are moved between ## 1. Current Active Tasks and ## 3. Pending Backlog, timeline history must be preserved.
Required behavior:
Timeline lines during migration.YYYY-MM-DD HH:MM) describing source and destination.Status, Created, Completed, Timeline) instead of collapsing into a single bullet summary.Protocol ID:
DDE-Task-Closer v1.6
Each project must begin in a new conversation window.
If project identifier changes inside conversation:
PROJECT_CONTEXT_VIOLATION
Stop.