incident-response

To create an incident runbook for a P0 outage, this Skill automates the generation of detailed response guides based on severity classification. It structures service checks, rollback procedures, and communication steps to ensure critical operations are followed during critical incidents.

A post-mortem template provides a structured format for analyzing incidents and identifying root causes after an outage. It ensures lessons are learned by systematically documenting the response timeline, findings, and per-incident records for future operational reference.

Classifying incident severity during operational triage involves using established runbook procedures to categorize impact. This Skill supports operational workflows by generating documentation that defines severity levels and guides the corresponding triage execution.

Yes, automating incident response documentation requires configuration of company settings and existing RFCs for context. These inputs provide the necessary operational background to accurately generate runbooks, per-incident records, and post-mortem templates.

Yes, you can execute service status checks and artifact validation during triage using the integrated operational scripts. These tools support the incident response workflow by validating artifacts and checking system status to guide rollback procedures.

An automated incident response process should be used when handling critical incidents to minimize downtime and establish repeatable operations. It replaces manual tracking by consistently generating runbooks, severity classifications, and post-mortem records across various platforms.