postmortem

Generate a postmortem report by providing session notes to summarize outcomes, failures, and root causes. The skill applies a postmortem template to structure sections and outputs a Markdown report directly in chat.

Capturing lessons learned is done by summarizing a coding session's outcomes into a concise postmortem report. This process highlights failures, inefficiencies, and root causes so teams can learn and improve.

Yes, you can rank improvements for the next session. The report generation process includes prioritizing actions, allowing teams to focus on the most critical improvements derived from the session's root-cause analysis.

No, the postmortem report does not edit project files. It outputs a Markdown report suitable for chat or documentation, ensuring your project file structure remains untouched while capturing session insights.

A postmortem template for root-cause analysis should include sections for summarizing outcomes, capturing failures, identifying root causes, documenting lessons learned, and listing prioritized improvements.

You need a postmortem report at the end of a session to capture failures, root causes, and lessons learned. It streamlines reflection by generating a concise summary of outcomes and prioritized improvements.