Live Incident Response

This is a Hermes-native live-incident-response workflow skill.

Why This Exists

live-incident-response exists because an incident that is still open had no owner. support-operations sent an active incident to reliability-review, and reliability-review reviews incident notes after the fact, so the one skill that saw the request handed it to a postmortem while the outage was still running.

Do Not Use When

• The incident is over and the request is the postmortem, the SLO or error-budget consequence, or remediation follow-up; use reliability-review.
• The request is one customer's support case needing a reply, a severity opinion, and an escalation path, with no incident declared; use support-operations.
• The request is a release being rolled out and watched -- deploy checklist, health signals, rollback criteria -- and nothing has been declared broken; use deploy-and-monitor.
• The request is to send the page, publish the status-page update, or deliver the customer notice; use connector-operator, which records a send as observed only on a returned result.
• The request asks whether a release is ready across rollout, rollback, and observability, before anything broke; use production-audit.

Examples

Good example: