Menú
【何时触发】：当用户明确要求修改、重构或新增具体的代码文件（如 .py, .cpp 脚本）时。 【不该触发】：当仅仅是在讨论思路或仅修改 .md 文档时。 【核心功能】：强制执行双阶段代码修改协议（Two-Phase Lifecycle）。第一阶段必须输出包含【修改原因、原逻辑、预期新效果、第一性原理审查】的 Proposal 且禁止写入文件。必须强制等待用户回复 `[APPROVED]` 后，才能进入第二阶段执行实际的文件写入。
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
【何时触发】：当用户在一个新的对话窗口中要求“了解项目”、“开始新需求”、“设计新模块”、“分析架构”，或者当用户要求修改/审查 /docs 目录下的 Layer 0-4 规范文档时。 【不该触发】：当明确要求修改 .py 或 .cpp 业务代码文件时。 【核心功能】：强制执行 DDE-Bootstrap 协议。扫描现有文档，进行 First-Principles 审查，拒绝模糊假设。若有需求变更，必须走 RFC 提案流程并等待 [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.
DDE subordinate extension. Execute verification loop (build/type/lint/test/security/diff) and return a structured quality report.
| name | dde-code-guard |
| description | 【何时触发】：当用户明确要求修改、重构或新增具体的代码文件（如 .py, .cpp 脚本）时。 【不该触发】：当仅仅是在讨论思路或仅修改 .md 文档时。 【核心功能】：强制执行双阶段代码修改协议（Two-Phase Lifecycle）。第一阶段必须输出包含【修改原因、原逻辑、预期新效果、第一性原理审查】的 Proposal 且禁止写入文件。必须强制等待用户回复 `[APPROVED]` 后，才能进入第二阶段执行实际的文件写入。 |
You are operating under: Documentation-Driven Engineering Code Modification Protocol (DDE-Code-Guard v1.3)
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
Any modification to actual codebase files MUST follow this two-phase lifecycle:
Phase 1: Proposal (NO WRITING TO DESK ALLOWED) You must output:
Phase 2: Execution
You must wait for the human to reply: [APPROVED].
Only then are you authorized to use file-writing tools to modify the code.
If a subordinate extension skill (for example: search-first, verification-loop, cpp-testing, python-testing) reaches a point where file writes are required:
[APPROVED] before any write.