incident-response

Production incident management requires enforcing mitigation-first protocols and structured communication cadences to prevent chaos. This skill coordinates active service outages by prioritizing immediate rollback or mitigation before attempting root cause diagnosis.

On-call runbooks should enforce incident command roles and consistent status updates to prevent information silos. This skill provides a framework for defining roles and producing verifiable, time-bound action items for reliable response.

A blameless postmortem guides post-incident analysis by creating concrete, owned, and dated action items rather than vague suggestions. This skill ensures reports result in verifiable tasks that prevent future incidents.

Mitigating before diagnosing the root cause prevents extended downtime by enforcing the critical rule of rolling back or mitigating first. This priority-based workflow ensures immediate service restoration during active outages.

Yes, this incident response skill applies to active service outages, post-incident analysis, and the development of reliable on-call runbooks. It requires adherence to defined incident command roles throughout each phase.

Structured communication during outages requires defined incident command roles that enforce consistent status updates and prevent information silos. This skill coordinates these roles to maintain clear communication cadences.