メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/tangziwen/CubeMiniGame --skill cp-applyコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
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.
| name | cp-apply |
| description | 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. |
| disable-model-invocation | true |
Before acting, read:
../_shared/codeplan/core.md../_shared/codeplan/step-contract.mdImplement exactly one stepX.md at a time. Run preflight checks first to detect repeated or partially-applied work before editing.
Before editing, read:
AGENTS.mdCodePlan/<PlanName>/design.mdCodePlan/<PlanName>/progress.mdstepX.mdRead other step files only when the current step explicitly depends on them.
Use the shared step-contract.md preflight state rules before editing.
Use the shared step-contract.md progress update shape.
After marking the current step complete, check whether all steps in progress.md are now checked.
If this was the final step:
CodePlan/<PlanName> 的所有步骤已完成).是否需要对当前 CodePlan 进行校验？) and wait for the user's answer before starting verification.If this was not the final step, continue normally and do not ask for whole-plan verification.
Prefer non-build verification:
rgIf compilation would be the only strong verification, say it was intentionally not run.
Summarize: