| id | SKL-incident-INCIDENTRETROSPECTIVE |
| name | Incident Retrospective |
| description | A postmortem (also called incident review or retrospective) is a structured process for analyzing incidents to understand what happened, why it happened, and how to prevent similar incidents in future |
| version | 1.0.0 |
| status | active |
| owner | @cerebra-team |
| last_updated | 2026-02-22 |
| category | Backend |
| tags | ["api","backend","server","database"] |
| stack | ["Python","Node.js","REST API","GraphQL"] |
| difficulty | Intermediate |
Incident Retrospective
Skill Profile
(Select at least one profile to enable specific modules)
Overview
A postmortem (also called incident review or retrospective) is a structured process for analyzing incidents to understand what happened, why it happened, and how to prevent similar incidents in future. The goal is learning, not blaming.
Core Principle: "Blame system, not person. Every incident is an opportunity to learn and improve."
Why This Matters
- Psychological Safety: Engineers feel safe reporting issues
- Honest Analysis: Root causes are identified without blame
- Organizational Learning: Knowledge is shared and documented
- System Improvement: Action items prevent recurrence
- Cultural Shift: Failures become learning opportunities
- Reduced MTTR: Better response procedures over time
Core Concepts & Rules
1. Core Principles
- Follow established patterns and conventions
- Maintain consistency across codebase
- Document decisions and trade-offs
2. Implementation Guidelines
- Start with the simplest viable solution
- Iterate based on feedback and requirements
- Test thoroughly before deployment
Inputs / Outputs / Contracts
- Inputs:
- Incident timeline and logs
- Monitoring data and metrics
- System architecture and configuration
- Entry Conditions:
- Incident is resolved and stable
- Root cause investigation is complete
- Team has time allocated for analysis
- Outputs:
- Postmortem document with findings
- Action items with owners and deadlines
