Run an Amazon-style Correction of Errors (COE) post-mortem on a development process failure. Produces a structured document with summary, timeline, five-whys root cause analysis, lessons learned, and typed action items — then offers to implement the fixes. Use this whenever something goes wrong in the dev process: a feature passes tests but doesn't actually work, functionality gets clobbered by a merge, an implementation is declared done but breaks on basic cases, a regression slips through, QA finds something that should have been caught earlier, or any incident that reveals a gap in the process. Invoke as /post-mortem or /coe with an optional brief description: e.g., `/post-mortem intake form broke after merging 3 PRs` or just `/coe`. Don't wait for the user to ask — if something went wrong, suggest running /post-mortem proactively.
2026-03-19