メニュー
Review CodePlan documents, including explored requirements, design.md, progress.md, and step files. Use when the user asks to review a plan, design, refinement, step breakdown, progress state, or readiness before implementation.
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 | cp-review |
| description | Review CodePlan documents, including explored requirements, design.md, progress.md, and step files. Use when the user asks to review a plan, design, refinement, step breakdown, progress state, or readiness before implementation. |
| disable-model-invocation | true |
Before acting, read:
../_shared/codeplan/core.md../_shared/codeplan/step-contract.md when reviewing stepX.md or progress.mdReview CodePlan documents and planning quality. Do not review implementation code with this skill; use cp-verify for code-vs-step verification.
Prefer targeted review over whole-plan review, but support whole-plan review at design gates and milestones.
Use the smallest scope that answers the user:
design.md before refinementstepX.md before applyprogress.md when status looks inconsistentcp-refinePrioritize:
File Operations lists that are missing, vague, incomplete, or too far below the top of a stepX.mdprogress.mdWhen reviewing stepX.md, explicitly check File Operations against step-contract.md. Report any missing, vague, or incomplete File Operations list as a review finding.
Lead with findings, ordered by severity. Include file and line references when possible.
If there are no findings, say so clearly and mention residual risks or unverified areas.
Do not modify files during review unless the user explicitly asks.