Incident Response

Purpose

Establish a structured incident response framework with clear severity levels, defined roles, documented runbooks, and a blameless postmortem culture to minimize recovery time and prevent recurrence.

Agent Protocol

Trigger

"incident response", "on-call", "PagerDuty", "OpsGenie", "incident management", "postmortem", "runbook", "severity", "escalation", "SEV", "SEV1", "SEV2", "SEV3", "incident command", "IC role", "incident timeline", "blameless postmortem", "incident lifecycle", "incident detection", "incident mitigation", "MTTD", "MTTR".

Input Context

• Current incident state (detected, ongoing, mitigated, resolved)
• Service affected and current impact (users down, degraded, partial)
• Severity level if already classified
• Team structure and on-call rotation
• Existing runbooks and their locations
• Communication channels (Slack, Teams, PagerDuty)
• Compliance requirements (SOC2, PCI, HIPAA postmortem timelines)