ridendine-incident-response

Production outage incident response requires guiding an incident commander through detection, triage, communication, investigation, mitigation, resolution, and postmortem. This Skill provides a structured workflow to minimize downtime and coordinate resolution efforts for web app emergencies.

Runbooks for database performance degradation and payment processing failures provide specific, actionable steps to diagnose and mitigate common production issues. They cover critical scenarios including deployment errors, offering clear procedures to restore service quickly during an incident.

Rollback procedures for Vercel, EAS mobile, Supabase migrations, and edge functions detail specific steps to revert changes across these platforms. These procedures are integrated into the incident response workflow to enable immediate mitigation during deployment-related production outages.

A blameless postmortem is a structured analysis conducted after resolving security incidents or other production outages, focusing on learning rather than assigning fault. This Skill provides a postmortem template to facilitate thorough analysis and actionable improvements following incident resolution.

Yes, this incident response workflow is designed for P0 critical outages where the web app is unreachable. It guides the incident commander through immediate diagnostic steps, stakeholder communication, and initiating a rollback or fix to restore service.

Pre-defined communication templates for production outage alerts, status updates, and resolutions are provided. These templates ensure clear, consistent messaging across defined communication channels throughout the incident response lifecycle, keeping stakeholders informed.