incident

Manage production incident response with triage, containment, and postmortem documentation.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill incident-rune-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/Rune-kit/rune/tree/main/skills/incident
Command: npx skills add https://github.com/Rune-kit/rune --skill incident-rune-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, step-by-step process for responding to production incidents, ensuring critical issues are triaged, contained, and resolved efficiently, while also documenting the entire process for postmortem analysis.

Core Features & Use Cases

  • Triage Severity: Classifies incidents into P1, P2, or P3 based on impact.
  • Containment Strategies: Offers various methods like rollback, feature flagging, or traffic shifting to stabilize the system.
  • Root Cause Analysis: Integrates with other skills to identify the underlying cause.
  • Postmortem Generation: Creates a detailed report including timeline, root cause, and prevention actions.
  • Use Case: When a critical service goes down, this skill will guide the response, ensuring quick containment and thorough documentation.

Quick Start

Use the incident skill to respond to a production outage.

Frequently Asked Questions about incident

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

FAQPage Schema
What is structured incident response and when do I need it for production issues?

Structured incident response systematically triages, contains, and resolves production issues. You need it when critical services go down, requiring quick stabilization, root-cause analysis, and thorough postmortem documentation.

How do I triage production issues and classify incident severity?

Triage production issues by classifying incident severity into P1, P2, or P3 based on system impact. This classification dictates the response workflow, enforcing containment before root-cause analysis and mandating postmortem generation for P1 and P2 incidents.

What are the best containment strategies for stabilizing a service during an outage?

Effective containment strategies for stabilizing a service during an outage include rollback, feature flagging, or traffic shifting. These methods isolate production issues and enforce system stability before proceeding to root-cause analysis.

How do I generate a postmortem report after resolving a P1 incident?

Generate a postmortem report after resolving a P1 incident by documenting the timeline, root cause, and prevention actions. The structured incident response workflow mandates postmortem generation automatically for all P1 and P2 production issues.

Does incident response workflow require root-cause analysis before containment?

No, incident response workflow strictly enforces containment before root-cause analysis. You must stabilize the system using containment strategies like rollback or traffic shifting before attempting to identify the underlying cause of production issues.