菜单
Use when tracked work hits a failing check, flaky result, runtime bug, or unexplained behavior and you need root cause before changing code.
用 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-debug |
| description | Use when tracked work hits a failing check, flaky result, runtime bug, or unexplained behavior and you need root cause before changing code. |
Debug by evidence and hypothesis, not patch roulette.
Do not start broad fixes before reproducing or characterizing the failure well enough to distinguish symptom from cause.
If the current evidence does not isolate the failure mode, gather more evidence first.
Do not propose or apply speculative fixes before Phase 1 has produced a concrete failure model.
Use when:
.superplan/gotchas.md.superplan/decisions.mdOnce root cause is clear, execution may continue through superplan-execute.
If the investigation reveals structural drift, hand back to superplan-shape.