postmortem-rca

Automate blameless postmortem workflows with standardized timelines and RCA reporting.

Updated May 11, 2026

Search Tags:#timeline #postmortem #runbooks #incident #blameless #rca #action-items

Ready to run

npx skills add https://github.com/resultakak/argos --skill postmortem-rca

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem-rca
Source: https://github.com/resultakak/argos/tree/main/skills/postmortem-rca
Command: npx skills add https://github.com/resultakak/argos --skill postmortem-rca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes blameless postmortems and RCA reporting to guide teams from incident trigger to concrete follow-up work.

Core Features & Use Cases

5 Why rooted analysis drives systemic understanding rather than personal blame.
Timeline & evidence collection ensures UTC traceability and repeatable process.
Follow-through planning creates owner assignment, due dates, and publish-ready documentation for stakeholders.

Quick Start

Trigger a new postmortem workflow and fill in the sections per this template as you analyze an incident.

Frequently Asked Questions about postmortem-rca

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

FAQPage Schema

How do I conduct a blameless postmortem for a production incident?▼

A blameless postmortem standardizes incident analysis by structuring timelines and applying 5-Why techniques to identify systemic contributing factors, ensuring teams focus on process improvement rather than personal blame.

What is the 5-Why method for root cause analysis in software engineering?▼

The 5-Why method for root cause analysis drives systemic understanding by iteratively asking why an incident occurred. It moves beyond surface symptoms to uncover underlying contributing factors and generate actionable preventative items.

How do I structure an incident timeline with UTC traceability?▼

Structuring an incident timeline with UTC traceability involves collecting evidence sequentially to ensure repeatable processes. This standardizes the documentation of events leading up to and during a customer-impacting bug.

Can I use this RCA workflow for near-misses and customer-impacting bugs?▼

Yes, this RCA workflow applies to production incidents, near-misses, and customer-impacting bugs. It guides teams through timeline creation, contributing factor analysis, and follow-through planning regardless of severity.

How do I assign owners and due dates for postmortem action items?▼

Assigning owners and due dates for postmortem action items involves structured follow-through planning. This creates clear accountability and produces publish-ready documentation for stakeholders to track remediation progress.

What is the best way to write publish-ready RCA documentation for stakeholders?▼

The best way to write publish-ready RCA documentation is to enforce structured requirements for blameless language, clear action item owners, and concrete due dates. This standardizes reporting from incident trigger to follow-up.