kwp-engineering-incident-response

Manage incident response lifecycle with triage, status updates, and postmortem generation.

7|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-incident-response
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kwp-engineering-incident-response
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/kwp/engineering/incident-response
Command: npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-incident-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the high-pressure, chaotic nature of incident management by providing a structured, repeatable framework for triage, status updates, and blameless postmortem documentation.

Core Features & Use Cases

  • Incident Lifecycle Management: Orchestrates the entire incident flow from initial detection and severity assessment to final resolution and postmortem analysis.
  • Standardized Communication: Generates consistent, factual status updates and professional postmortem reports to ensure stakeholder alignment.
  • Use Case: When a production service experiences an outage, use this skill to quickly assess severity, track mitigation steps in real-time, and generate a blameless postmortem document once the service is restored.

Quick Start

Initiate a new incident response workflow by telling the agent that production is currently down.

Frequently Asked Questions about kwp-engineering-incident-response

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

FAQPage Schema
How do I automate incident triage and severity assessment during a production outage?

To automate incident triage during a production outage, this Skill orchestrates the incident response lifecycle by assessing severity and tracking mitigation steps. It requires integration with monitoring platforms to automate alert ingestion and initial severity evaluation.

How do I generate a blameless postmortem document after resolving a service disruption?

Generating a blameless postmortem document after a service disruption is handled by reconstructing the incident timeline and performing root cause analysis. The Skill standardizes this documentation to ensure factual, professional reporting for stakeholder alignment.

What is the best way to standardize incident status updates for stakeholders during an SRE incident?

Standardizing incident status updates for stakeholders during an SRE incident involves generating consistent, factual communications throughout the disruption. This Skill manages real-time status updates to maintain alignment across technical teams and stakeholders.

Does this incident response workflow require integration with existing monitoring platforms?

Yes, this incident response workflow requires integration with incident management or monitoring platforms. This integration is necessary to automate alert ingestion, track mitigation steps, and push automated status updates throughout the incident lifecycle.

Can I use this Skill to reconstruct an incident timeline for root cause analysis?

Yes, you can use this Skill to reconstruct an incident timeline for root cause analysis. It supports technical teams by documenting mitigation steps and mapping the timeline to facilitate blameless postmortem generation after service restoration.

When do I need a structured DevOps incident response framework?

You need a structured DevOps incident response framework when managing the high-pressure, chaotic nature of service disruptions. This Skill provides a repeatable process for triage, status communication, and postmortem documentation during production outages.