incident-response

Automating incident response workflows involves stabilizing affected services, gathering factual evidence, assigning roles like incident commander, and generating structured status updates. This Skill enforces guardrails for evidence preservation and provides templates for consistent incident updates during SEV incidents.

Coordinating roles during a SEV incident requires clearly assigning an incident commander, comms lead, and tech lead. This workflow automates role assignment, tracks mitigations and follow-ups, and logs consistent status updates to keep all stakeholders informed throughout the production issue.

Yes, this incident response workflow is designed for inclusion in enterprise runbooks and integrates with monitoring dashboards for evidence collection. It gathers facts from your existing infrastructure to stabilize services and produce structured post-incident notes.

Yes, this workflow applies to outages and SEV incidents across multiple services. It stabilizes services, gathers facts, and tracks mitigations regardless of the number of services impacted by the production issue.

To start the incident response workflow, provide an incident title to initiate the process. The workflow will then generate an incident plan, assign necessary roles, and produce structured status updates to guide your response.

This workflow requires a provided incident title to initiate and focuses on stabilizing services, gathering facts, and producing status updates. It enforces guardrails for evidence preservation and clear next steps, but relies on integration with your existing runbooks and monitoring dashboards for evidence collection.