メニュー
Use when you are about to say work is complete, fixed, passing, or ready and need fresh proof from the real workspace harness first.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when routed repo work still has meaningful ambiguity about behavior, constraints, taste, or acceptance intent, and that ambiguity would make planning or execution unsafe.
Use when a new request might involve repo work, tracked changes, workspace-specific decisions, or durable coordination and you must decide whether Superplan should engage before exploring or implementing.
Use when tracked work is already shaped and the next move is to execute, verify, block, or request feedback without replanning from scratch.
Use when the target is understood but the work still needs an execution path, task breakdown, or proof strategy before implementation begins.
Use when Superplan may engage and you need to decide whether to stay lightweight, create one tracked task, gather context first, or shape deeper structure before execution begins.
Use when Superplan has decided to engage and the work still needs plans, specs, proof paths, or multiple tracked tasks shaped before bounded execution can start.
| name | superplan-verify |
| description | Use when you are about to say work is complete, fixed, passing, or ready and need fresh proof from the real workspace harness first. |
Do not claim success without evidence.
This is the generic discipline gate that runs before completion claims. It is not the same as Superplan's final AC review, but it feeds that review.
No claim of complete, fixed, passing, or ready for handoff without running the relevant proof first.
Do not use confidence, code inspection, or stale output as a substitute for fresh verification evidence.
Use when:
superplan-review when tracked task completion is at stakeFor tracked tasks, verification hands into superplan-review.
For non-tracked work, it still governs whether any success claim is honest.