القائمة
Use when someone asks whether the current product slice is ready to ship, publish, or recommend and the answer depends on a disciplined release-quality check.
التثبيت باستخدام 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-release |
| description | Use when someone asks whether the current product slice is ready to ship, publish, or recommend and the answer depends on a disciplined release-quality check. |
Decide whether the current product slice is honestly ready to ship.
Use when:
Likely follow-ons:
superplan-verify for missing proofsuperplan-docs for stale release docssuperplan-execute for the concrete blocker fixes