incident-postmortem

Document root causes of agentic and system failures with structured RCA reports.

Updated May 2, 2026
One-click install
npx skills add https://github.com/artgaurav16420-oss/Mega-Skills --skill incident-postmortem-artgaurav16420-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/artgaurav16420-oss/Mega-Skills/tree/main/distribution/harnesses/tabnine/agent/skills/incident-postmortem
Command: npx skills add https://github.com/artgaurav16420-oss/Mega-Skills --skill incident-postmortem-artgaurav16420-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blamelessly analyzes production incidents to produce structured post-mortems that illuminate root causes and prevent recurrence.

Core Features & Use Cases

  • Structured RCA framework: evidence gathering, timeline construction, root cause analysis, and action items.
  • Guardrails and learning artifacts: ensures traceability and accountability with assigned owners and measurable completion criteria.
  • Use Case: when a production failure occurs in an agent or tool integration, generate a learning artifact to guide fixes and improvements.

Quick Start

Provide a step-by-step postmortem workflow for a recent incident using captured logs and traces to generate an action-driven RCA report.

Frequently Asked Questions about incident-postmortem

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

FAQPage Schema
What is a blameless incident postmortem and when do I need to generate one?

A blameless incident postmortem is a structured review that identifies and documents root causes of production failures to prevent recurrence. You need this process when analyzing agentic failures, tool-call loops, or performance regressions across distributed agent ecosystems.

How do I conduct a root cause analysis for production incidents using captured logs and traces?

To conduct root cause analysis for production incidents, provide captured logs and traces to step through a structured workflow: gather evidence, construct a timeline, analyze the root cause, and generate an action-driven report with assigned owners and completion criteria.

Can I use this incident response framework for agent tool-call loops and performance regressions?

Yes, this incident response framework applies directly to agent tool-call loops and performance regressions. It analyzes failures across distributed agent ecosystems to produce learning artifacts that guide system fixes and improvements.

What is the best way to ensure traceability and accountability in an RCA report?

The best way to ensure traceability and accountability in incident reviews is to generate structured postmortems with concrete action items, assigning specific owners and defining measurable completion criteria for every guardrail and learning artifact.

Does this blameless postmortem process require any specific dependencies or environment setup?

No specific dependencies are required to perform this blameless postmortem process. You only need to supply captured logs and traces from your recent incident to begin the evidence gathering and timeline construction workflow.

Why should I not just fix the bug immediately instead of writing an incident postmortem?

Fixing a bug immediately without an incident postmortem risks recurrence because it skips root cause analysis. Generating a learning artifact ensures traceable conclusions and builds guardrails to prevent the same system failure across distributed ecosystems.