incident-management

Coordinates incident response workflows and assigns Incident Commanders for production service disruptions.

3|Updated Apr 14, 2026

Search Tags:#incident management #response coordination #alert management #on-call rotation #postmortem analysis

Ready to run

npx skills add https://github.com/MayaDispeler/TheOrqestra --skill incident-management-mayadispeler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-management
Source: https://github.com/MayaDispeler/TheOrqestra/tree/main/skills/incident-management
Command: npx skills add https://github.com/MayaDispeler/TheOrqestra --skill incident-management-mayadispeler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines incident response and management processes for engineering organizations, ensuring timely and effective resolution of production system issues.

Core Features & Use Cases

Incident Coordination: Assigns a single Incident Commander to manage and coordinate incident response activities.
Mitigation and Resolution: Prioritizes immediate mitigation to stop user harm and addresses root causes for long-term resolution.
Documentation and Analysis: Requires factual, timestamped incident timelines and mandatory postmortems for learning and improvement.
Alert Management: Ensures alert thresholds are set and maintained to prevent alert fatigue and ensure critical issues are not missed.
On-Call Management: Requires on-call engineers to have runbooks for every alert and maintains on-call rotation coverage to mitigate risk.

Quick Start

Start an incident response process by declaring a SEV1 or SEV2 incident, assign an Incident Commander, and follow the documented steps for mitigation and resolution.

Frequently Asked Questions about incident-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate incident response to ensure timely resolution of production issues?▼

Incident response coordination is managed by assigning a single Incident Commander to oversee mitigation activities, prioritize stopping user harm, and document factual timelines for long-term root cause resolution.

What is the best way to manage on-call rotation and prevent alert fatigue?▼

Alert fatigue is prevented by maintaining strict alert thresholds and ensuring on-call engineers have runbooks for every alert, while on-call rotation coverage is actively maintained to mitigate operational risk.

How do I start a SEV1 or SEV2 incident management workflow?▼

Start an incident management workflow by declaring a SEV1 or SEV2 incident, assigning an Incident Commander, and following documented steps to coordinate communication and decision-making for mitigation.

How does postmortem analysis work after resolving a service disruption?▼

Postmortem analysis requires factual, timestamped incident timelines to be documented during the event, which then serve as the basis for mandatory post-incident learning and process improvement.

Do I need runbooks for every alert during on-call management?▼

Runbooks are required for every alert during on-call management to ensure engineers can systematically address triggered alerts and mitigate risk during service disruptions.