القائمة
Use when work is pausing, switching owners, or at risk of context loss and the next agent will need a concise restart point with the current truth.
التثبيت باستخدام 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-handoff |
| description | Use when work is pausing, switching owners, or at risk of context loss and the next agent will need a concise restart point with the current truth. |
Preserve momentum when work changes hands.
Use when:
Typical resume path:
superplan status --jsonsuperplan run --jsonsuperplan run --jsonsuperplan task inspect show <task_ref> --json only when the handoff points to a specific task you need to inspect directly