post-mortemlisted

# Post-Mortem Skill > **Purpose:** Wrap up completed work — validate it shipped correctly, extract learnings, process the knowledge backlog, activate high-value insights, and retire stale knowledge. > > **Runtime note:** Hook-driven closeout is runtime-dependent. Claude/OpenCode can wire Phase 2-5 maintenance through lifecycle hooks. Codex does not expose that hook surface, so Codex sessions should finish closeout with `ao codex ensure-stop`. Six phases: 1. **Council** — Did we implement it correctly? 2. **Extract** — What did we learn? 3. **Process Backlog** — Score, deduplicate, and flag stale learnings 4. **Activate** — Promote high-value learnings to MEMORY.md and constraints 5. **Retire** — Archive stale and superseded learnings 6. **Harvest** — Surface next work for the flywheel --- ## Quick Start ```bash $post-mortem # wraps up recent work $post-mortem epic-123 # wraps up specific epic $post-mortem --quick "insight" # quick-capture single learning (no council) $post-mortem --process-only # skip council+extraction, run Phase 3-5 on backlog $post-mortem --skip-activate # extract + process but don't write MEMORY.md $post-mortem --deep recent # thorough council review $post-mortem --mixed epic-123 # cross-vendor (Claude + Codex) $post-mortem --skip-checkpoint-policy epic-123 # skip ratchet chain validation ``` ### Codex Closeout In Codex hookless mode, run these after the post-mortem workflow writes learnings and next wor