원클릭으로
memo-continue
继续编辑 `.memo/` 目录下已有的记录文件。 用户未指定文件时,先查找最近修改的文件,询问用户是否使用该文件; 若用户明确说“最新”或“latest”,则直接使用最近修改的文件。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
继续编辑 `.memo/` 目录下已有的记录文件。 用户未指定文件时,先查找最近修改的文件,询问用户是否使用该文件; 若用户明确说“最新”或“latest”,则直接使用最近修改的文件。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Assess whether completed engine code changes should be reflected in Doc/EngineCodeMap. Use implicitly only after C/C++ source or header file changes under CubeEngine/EngineSrc, such as .c, .cc, .cpp, .cxx, .h, .hh, .hpp, .hxx, .inl, or .ipp, and only when the change may alter durable module responsibilities, important objects, or stable entry points that help narrow source search. Ignore doc-only, build-only, asset-only, config-only, generated, formatting, and other non-code-file changes unless the user explicitly asks to evaluate CodeMap. Also use when the user says "更新codemap", "update codemap", or otherwise explicitly asks to update or sync CodeMap. First filter out pure bug fixes, tiny helper-only changes, formatting, generated files, assets, build-only changes, and implementation-only refactors that do not change AI navigation value. If classified as skip, do not ask the user; only ask before editing when a real CodeMap update is likely needed.
Assess whether completed CubeGame gameplay changes should be reconciled into Doc/GameplayIntent design documents. Use implicitly only after C/C++ source or header file changes under CubeEngine/Application/CubeGame, such as .c, .cc, .cpp, .cxx, .h, .hh, .hpp, .hxx, .inl, or .ipp, and only when the change may alter gameplay design intent, concrete design mechanisms, concepts, object relationships, aliases, or Concept Code Anchors. Ignore doc-only, build-only, asset-only, config-only, generated, formatting, and other non-code-file changes unless the user explicitly asks to evaluate gameplay design docs. First filter out pure engine/non-gameplay changes, then list candidate concept changes and ask the user before editing design docs. Do not use for pure engine changes, pure rendering/backend changes, ordinary bug fixes, helper/config/data-only additions, or implementation-only refactors that do not change gameplay concepts.
Apply exactly one CodePlan step to the repository, with preflight idempotency checks and progress.md updates. Use when the user asks to execute, apply, continue, or implement a specific step or the next unchecked step.
Explicitly verify CubeGame gameplay code against Doc/GameplayIntent design documents. Use only when the user asks to verify, audit, review, or check whether gameplay implementation matches accepted design intent. This is one-way verification: if code and intent disagree, report or fix code; never rewrite intent documents to match the current code unless the user separately asks for design sync.
Build the project using the CMake presets defined for this repository. Use when the user asks to compile, build, or verify that the project builds.
Explore and clarify a prospective CodePlan before writing design.md. Use when the user has a rough requirement and wants read-only investigation, clarifying questions, constraints discovery, and a compact candidate CodePlan name before running cp-plan.
| name | memo-continue |
| category | productivity |
| disable-model-invocation | true |
| description | 继续编辑 `.memo/` 目录下已有的记录文件。 用户未指定文件时,先查找最近修改的文件,询问用户是否使用该文件; 若用户明确说“最新”或“latest”,则直接使用最近修改的文件。 |
帮助用户定位并继续编辑 .memo/ 目录下已有的记录文件。
.memo/ 目录:
ls -lt 或等效方式列出 .memo/*.md 文件,按修改时间排序。char-balance.md”)→ 直接读取该文件。char-balance.md?(修改时间:2025-06-07)”最近修改的记录是:
- 文件名:char-balance.md
- 修改时间:2025-06-07
是否继续编辑这个文件?(回复“是”或“最新”即可直接打开;也可以告诉我你想编辑哪个文件)
用户:继续编辑
→ 系统列出 .memo/ 目录,发现最近修改的是 char-balance.md
→ 回复用户:
最近修改的记录是:
- 文件名:char-balance.md
- 修改时间:2025-06-07
是否继续编辑这个文件?(回复“是”或“最新”即可直接打开;也可以告诉我你想编辑哪个文件)
用户:继续最新的记录
→ 直接打开最近修改的文件,展示内容并等待用户编辑。
用户:继续编辑 ui-layout.md
→ 直接打开 .memo/ui-layout.md,展示内容并等待用户编辑。
.memo/ 目录为空时,提示用户没有现有记录,建议先使用 memo-write 创建。