incident-postmortem-generator

Generate incident postmortem and root-cause-analysis reports aligned with OCC and FFIEC standards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wassemgtk/skills-testing --skill incident-postmortem-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-postmortem-generator
Source: https://github.com/wassemgtk/skills-testing/tree/main/financial-services/governance-controls/incident-postmortem-generator
Command: npx skills add https://github.com/wassemgtk/skills-testing --skill incident-postmortem-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive incident postmortem reports for financial institutions, ensuring compliance with regulatory standards and facilitating thorough root cause analysis.

Core Features & Use Cases

  • Regulatory Compliance: Generates reports aligned with OCC, FFIEC, and COSO frameworks.
  • Root Cause Analysis: Employs structured methods like 5 Whys and Fishbone diagrams.
  • Impact Assessment: Quantifies customer, financial, regulatory, and reputational impacts.
  • Use Case: After a critical system outage, use this Skill to generate a board-ready postmortem report detailing the timeline, root cause, impact, and corrective actions, meeting regulatory deadlines.

Quick Start

Use the incident-postmortem-generator skill to create a postmortem report for a recent critical incident, providing the incident details, impact assessment, and root cause analysis.

Frequently Asked Questions about incident-postmortem-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an incident postmortem report for financial regulatory compliance?

To generate a compliant incident postmortem report, this Skill analyzes operational incidents, documents root causes, assesses impacts, and defines corrective actions aligned with OCC Heightened Standards, FFIEC guidance, and the Three Lines of Defense model.

What root cause analysis methods are used for operational incidents in banking?

Root cause analysis for banking operational incidents utilizes structured methods like the 5 Whys and Fishbone diagrams to identify underlying issues and define corrective actions for risk reduction.

How do I assess the impact of a critical system outage for a board-ready postmortem?

Impact assessment for a board-ready postmortem quantifies customer, financial, regulatory, and reputational impacts resulting from the critical system outage, ensuring all affected areas are documented for stakeholders.

Does this incident response postmortem generator align with OCC and FFIEC frameworks?

This incident response postmortem generator aligns directly with OCC Heightened Standards, FFIEC guidance, and COSO frameworks, ensuring financial institutions meet regulatory compliance and reporting deadlines.

When do I need a formal postmortem report for incident response?

A formal postmortem report is needed after any critical operational incident to document the timeline, root cause, impact, and corrective actions, facilitating regulatory compliance and reducing future risk.

Can I use this for risk management reporting under the Three Lines of Defense model?

Yes, you can use this for risk management reporting as it generates postmortems adhering to the Three Lines of Defense model, defining corrective actions that ensure regulatory compliance and operational risk reduction.