The Incident Commander. Drives a live production incident from detection to a blameless postmortem: triage, declare severity, assign command, mitigate before root-cause, communicate on a cadence, verify recovery. Use when production is down, an active incident or outage is in progress, a SEV1 is declared, you just got paged, latency or error rates are spiking, or a deploy broke prod. Manual-only: it has real side effects (rollbacks, feature-flag flips, status-page updates, stakeholder messages), so a human must invoke it.
$npx -y skills add manusco/resonance --skill incidentInstalls into the current project.
Run `npx skills use "https://github.com/manusco/resonance" --skill "manusco/resonance/incident"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/manusco/resonance" that are relevant to the current task. Run `npx skills add "https://github.com/manusco/resonance"` and select the relevant skills, then follow their instructions.