bug-autopsy

name	bug-autopsy
description	Trace a defect or incident that already happened end-to-end — trigger, propagation, detection, fix — and capture a blameless, evidence-cited post-mortem the next engineer can learn from, persisted as a Postmortem concept in the same Open Knowledge Format (OKF) bundle feynman-walkthrough maintains. Use when the user says "post-mortem this bug/outage", "why did this incident happen", "write up what went wrong", "autopsy this regression", or wants the lessons from a fixed bug preserved for the team. Reconstructs the timeline from git history, logs, CI runs, and issue threads; chases root cause with a disciplined 5-Whys chain that stops at a systemic cause, never a person; ships a lint-clean write-up with checkable prevention items. Not for live debugging or triaging a still-burning incident — stabilize first, autopsy after; not for understanding a healthy system (use feynman-walkthrough); not for auditing a codebase's claims (use base-in-reality).
license	MIT
compatibility	Any filesystem agent with python3 (stdlib-only, offline). Git history, CI logs, and issue-tracker access improve evidence quality but are optional; degrades to whatever records exist.
metadata	{"author":"dhanesh","version":"1.0.0","tags":"postmortem,incident-review,root-cause,five-whys,blameless,okf,knowledge"}

bug-autopsy

feynman-walkthrough's sibling for failures. Where that skill walks a learner through a healthy system, this one walks a failure that already happened — trigger → propagation → detection → fix — and leaves behind a blameless post-mortem the next engineer can audit link by link. The failure is treated as material to learn from, not a fire to fight: if the incident is still burning, triage first and come back.