Postmortem th

• ◦Give each action item an owner and due datein 25 of 209, across 23 files
• ◦Conduct blameless postmortem within 48 hoursin 13 of 209, across 10 files
• ◦Mitigate impact before investigating root causein 11 of 209, across 10 files
• ◦Apply Five Whys to identify root causein 11 of 209, across 9 files
• ◦Try rollback first when a recent deploy caused itin 9 of 209, across 8 files
• ◦Keep post-mortems blamelessin 8 of 209, across 7 files
• ◦Write blameless postmortems for all incidentsin 8 of 209, across 6 files
• ◦Create a runbook for every new alertin 8 of 209
• ◦Track action items to completionin 7 of 209
• ◦Run automated enumeration scripts like linPEAS or winPEASin 7 of 209, across 2 files
• ◦Update stakeholders every 15-30 minutesin 7 of 209, across 5 files
• ◦Give every action item an owner and priorityin 7 of 209

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.