Menu
Use when completed or failed work exposed a reusable lesson, recurring trap, or process weakness worth capturing for future tasks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-postmortem |
| description | Use when completed or failed work exposed a reusable lesson, recurring trap, or process weakness worth capturing for future tasks. |
Turn completed or failed work into reusable learning.
This skill exists to reduce repeated mistakes, not to assign blame.
Use when:
Do not use when:
.superplan/gotchas.md.superplan/decisions.mdLikely follow-ons:
superplan-guard when a test or proof path should be addedsuperplan-docs when the docs or help misled the worksuperplan-shape when the underlying task breakdown needs to change