incident-response

Name: incident-response
Availability: InStock
Author: sun2443

Manages incident response workflows from detection through postmortem documentation.

Updated Apr 8, 2026

Search Tags:#postmortem #triage #root-cause-analysis #blameless #incident-response #status-update #severity-classification

Ready to run

npx skills add https://github.com/sun2443/designer-skills --skill incident-response-sun2443

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/sun2443/designer-skills/tree/main/engineering/skills/incident-response
Command: npx skills add https://github.com/sun2443/designer-skills --skill incident-response-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams respond to production incidents in a structured, repeatable way, reducing confusion during triage and improving the quality and usefulness of post-incident learning.

Core Features & Use Cases

Incident triage and severity classification: Assess impact, determine SEV1–SEV4, and identify affected systems and roles.
Communication workflow: Draft internal status updates and customer-facing messaging guidance at a clear cadence.
Postmortem generation: Produce a blameless postmortem including timeline reconstruction, root cause analysis (5 whys), and action items with owners.

Quick Start

Start a new incident by sending: /incident-response new The payment service is returning 500 errors for many users and dashboards look inconsistent.

Frequently Asked Questions about incident-response

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

FAQPage Schema

How do I run blameless postmortems after a production incident?▼

Blameless postmortems are generated by documenting the incident timeline, performing root cause analysis using the 5 whys method, and assigning action items with specific owners.

What is the best way to triage production alerts and classify incident severity?▼

Triage production alerts by assessing user impact and system health, then classify the event using SEV1 through SEV4 severity levels to guide the appropriate response workflow.

How do I structure incident status updates for internal teams and customers?▼

Incident status updates are structured through a communication workflow that drafts internal notifications and customer-facing messaging guidance at a clear, consistent cadence.

Can I use this incident response workflow for mid-incident mitigation tracking?▼

Yes, the incident response workflow supports mid-incident updates by tracking mitigation steps, assessing ongoing impact, and documenting status changes until the issue is resolved.

When do I need to trigger a postmortem for a resolved incident?▼

Trigger a postmortem when an incident is resolved and you need to formally document the timeline, establish root causes, and capture corrective action items for future prevention.