sre-postmortem

Generates blameless postmortems with 5-Whys analysis, Confluence pages, and Jira action items.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-postmortem-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-postmortem
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/ai-sre/skills/sre-postmortem
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-postmortem-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a production incident, teams struggle to reconstruct what happened, identify the true root cause, and document findings consistently. This Skill automates the blameless post-incident review process by pulling evidence from Jira, GitLab pipelines, and Kubernetes events, then producing a structured postmortem with actionable follow-ups. ## Core Features & Use Cases - Timeline Reconstruction: Gathers incident context from Jira tickets, GitLab pipeline history, and AKS pod events to build a UTC timeline with detection lag and MTTR metrics. - 5-Whys Root Cause Analysis: Applies structured root cause chains with product-specific examples, plus a contributing factors table covering monitoring, documentation, and configuration gaps. - Confluence & Jira Integration: Creates a postmortem page in the Confluence MI space and generates SMART action items as Jira sub-tasks linked back to the incident ticket. - Use Case: After resolving a push notification outage in Emergency Management, run the skill with the incident ticket key to produce a complete blameless postmortem page and tracked remediation tasks. ## Quick Start Run /ai-sre:sre-postmortem em SE-1234 to generate a blameless postmortem for the Emergency Management incident ticket SE-1234.

Frequently Asked Questions about sre-postmortem

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

FAQPage Schema
How do I create a postmortem from a Jira incident ticket?

Run /ai-sre:sre-postmortem with a product slug and Jira ticket key, such as /ai-sre:sre-postmortem em SE-1234. The skill fetches the ticket via JQL, gathers pipeline and Kubernetes context, and produces a Confluence postmortem page with action items.

How does the 5-Whys root cause analysis work in this skill?

The skill guides a structured 5-Whys chain starting from the observed symptom and drilling to the root cause, with product-specific examples like Azure Notification Hub secret expiry or KEDA scaling to zero. It stops when a process or monitoring gap is identified as the root cause.

Which products are supported for postmortem generation?

Supported products include Emergency Management, Training, Visitor Management, Volunteer, Dismissal, CPOMS StudentSafe and StaffSafe, SmartPass, SchoolPass, EventSafe, and Badge Alert. Each maps to an AKS namespace, GitLab project ID, and Jira label defined in the routing table.

Does the skill create Confluence pages and Jira tickets automatically?

Yes, it creates a postmortem page in the Confluence MI space under the Postmortems parent page, then asks before creating Jira sub-tasks for action items. It also adds a comment to the original incident ticket with the Confluence URL.

What happens if I run the postmortem skill without a Jira ticket?

If no ticket key is provided, the skill asks for the incident start and end time, user-facing impact, components involved, the fix applied, and a Jira ticket to link. It then proceeds with timeline reconstruction from that information.