skills.rest
cuongnm-dev
cuongnm-devCOMMUNITY
Explore all skills by this author →
GitHub

incident

Coordinate incident response and generate postmortem documentation for P0/P1 outages.

Updated Aug 27, 2026
Search Tags:#runbook#on-call#postmortem#sre#incident#incident-management#blameless
One-click install
npx skills add https://github.com/cuongnm-dev/team-ai-config --skill incident-cuongnm-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/cuongnm-dev/team-ai-config/tree/main/cursor/skills/incident
Command: npx skills add https://github.com/cuongnm-dev/team-ai-config --skill incident-cuongnm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When major outages occur, teams need a coordinated, blame-free process to triage, communicate, contain, and learn from incidents. This skill guides responders through dual modes (respond and postmortem) and provides a structured workflow to minimize downtime and accelerate remediation, while ensuring a thorough post-incident analysis.

Core Features & Use Cases

  • Real-time incident coordination: assigns roles, collects essential incident details, and tracks actions across SRE, DevOps, and communications.
  • Dual-mode operation: respond mode for active incidents and postmortem mode for blameless root-cause analysis after stability is restored.
  • Artifacts & runbooks: generates incident body, timelines, contributing factors, remediation plans, and postmortem documentation to be stored under docs/incidents/{incident-id}.md.
  • Outputs actionable guidance: escalation recommendations, SLO status checks, and structured incident reports for stakeholders.

Quick Start

Describe the incident details and initiate the respond workflow.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I coordinate a P0 or P1 incident response in real-time?▼

Coordinate real-time incident response by assigning roles like incident commander and SRE, collecting essential details, and tracking actions across DevOps and communications to minimize downtime.

What is a blameless postmortem and when do I need to write one?▼

A blameless postmortem is a structured root-cause analysis performed after an incident is resolved. You need it after high-severity outages to identify contributing factors without assigning individual blame.

How do I structure postmortem documentation for high-severity outages?▼

Structure postmortem documentation by generating an incident timeline, contributing factors, and remediation plans, saving the final report as a markdown file under the docs/incidents directory.

Can I use this incident management workflow for both active response and post-incident analysis?▼

Yes, the incident management workflow operates in dual modes: a respond mode for active incidents and a postmortem mode for blameless root-cause analysis after stability is restored.

What incident details are required to generate an incident ID and escalation plan?▼

Provide the incident description to generate a unique incident ID, assess impact, check SLO status, and outline structured escalation recommendations for stakeholders.

Does this incident management process require any specific external dependencies?▼

No, this incident management process has zero external dependencies and provides built-in runbooks for impact assessment, containment, remediation, and reporting out of the box.

Related Skills

Explore More Software Engineering Skills→
shiftreposhiftrepo

LogCollector

Collects incident logs via SSH from Excel task lists and generates reports.

Official
Intermediate
vecearvecear

postmortem-writer

Generate post-incident reports with timelines, root causes, and action items.

Community
Advanced
cyperx84cyperx84
2

Incident Response

Guide structured incident response from alert detection to post-mortem.

Community
Basic
chicanoandres702chicanoandres702

incident-response-incident-response

Coordinates automated, multi-agent incident response using SRE principles across distributed systems.

Community
Advanced