메뉴
Reviews an externally-authored implementation plan for quality, VGV conventions, and scope. Plans created by /plan are already reviewed during creation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Executes an implementation plan — writes code and tests, runs quality review, and ships a pull request.
Turns high-level brainstorming and ideas into well-structured, actionable implementation plans.
Applies a minimal, targeted fix for emergency bugs — enforces review and testing without brainstorm or planning phases.
Runs quality review agents on demand — reviews code against VGV standards for architecture, tests, and simplicity, then writes one consolidated, numbered report.
Explores requirements and approaches through collaborative dialogue before planning implementation.
Stage, commit, push, and open a pull request following project conventions and the Conventional Commits spec. Accepts optional skip-checks argument to bypass validation when called from /build.
| name | plan-technical-review |
| user-invocable | true |
| description | Reviews an externally-authored implementation plan for quality, VGV conventions, and scope. Plans created by /plan are already reviewed during creation. |
| when_to_use | Use to review a plan you did not create with /plan — a hand-written plan or one from another tool. Triggers on "review the plan", "is this plan ready", "validate my plan", or "check the plan". |
| argument-hint | path to plan file |
| effort | high |
| compatibility | Designed for Claude Code (or similar products with agent support) |
Review a plan that was not created by /plan. /plan runs this same review inline during
creation, so use this skill for externally-authored plans — hand-written, from another tool,
or from a teammate.
Plan file: $ARGUMENTS (if empty, ask the user for the plan path or pick the most recent file under docs/plan/).
Follow the plan review procedure with <PLAN_PATH> set to the
plan file. It runs the simplicity, VGV, and scope-splitting agents in parallel, applies their
findings to the plan inline, and resolves any scope-splitting recommendation.
After the review completes, use AskUserQuestion to present next steps:
Question: "Technical review complete! What would you like to do next?"
Options:
/buildIf the user selects "Clear context and build" → Follow the clear context handoff for /build with the actual plan file path. Then stop.
When invoked by another skill, return control to the caller after the review completes — do not present handoff options.