ワンクリックで
onex-plan-review
Adversarial pre-execution check on a plan file. Run this before execute_plan or manually.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Adversarial pre-execution check on a plan file. Run this before execute_plan or manually.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill when the user has a rough idea, wants to explore a feature, or says "let's brainstorm" or "help me design." The goal is to refine an idea into a validated design doc before any code is written.
Use this skill when ending a session and you want the next session to pick up where you left off. The goal is to capture enough context for seamless session continuity.
Use this skill when starting feature work that needs isolation from the current workspace, or when you need to work on multiple branches simultaneously. The goal is to create an isolated worktree with a verified clean baseline.
Use this skill when fixing a bug caused by invalid data reaching deep into execution. The goal is to add validation at every layer the data passes through, making the bug structurally impossible to reproduce.
Use this skill when documentation has drifted from the codebase, needs an inventory, or should be archived.
Autonomous implementation pipeline. Reads a plan file, reviews it adversarially,
| name | onex-plan-review |
| description | Adversarial pre-execution check on a plan file. Run this before execute_plan or manually. |
| disable-model-invocation | true |
Adversarial pre-execution check on a plan file. Run this before execute_plan or manually.
Announce at start: "I'm using the onex-plan-review skill."
/plan-review docs/plans/my-plan.md
Run all six checks. Classify each finding: CRITICAL, MAJOR, MINOR, NIT.
Scan numeric claims near "tasks", "steps", "phases". Recount from actual ## Task N: headings.
If any count claim ≠ actual count: CRITICAL.
For each task's acceptance criteria:
Can the task's stated scope implement everything it claims?
Tasks that create resources must state dedup mechanism:
Grade each verification step:
Weak-only proof for a core invariant → MAJOR. Pair with medium or strong.
After all checks:
Output format:
Plan Review: docs/plans/my-plan.md
R1: PASS R2: PASS R3: PASS R4: MINOR R5: PASS R6: PASS
Findings: 0 CRITICAL, 0 MAJOR, 1 MINOR, 0 NIT
Verdict: PASS