incident_response

Design incident response processes covering detection, communication, resolution, and blameless post-mortems.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/orqesa/orqesa-roles --skill incident-response-orqesa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident_response
Source: https://github.com/orqesa/orqesa-roles/tree/main/roles/cto/skills/incident-response
Command: npx skills add https://github.com/orqesa/orqesa-roles --skill incident-response-orqesa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive framework for managing technical incidents, ensuring swift resolution, clear communication, and continuous improvement through blameless post-mortems.

Core Features & Use Cases

  • Incident Management: Guides teams through detection, declaration, containment, and resolution of outages.
  • Communication Strategy: Offers templates and cadence for internal and external status updates.
  • Blameless Post-Mortems: Facilitates a culture of learning from failures by focusing on system improvements rather than individual blame.
  • Use Case: When a critical service experiences an outage, this Skill helps the team establish roles, communicate effectively with stakeholders, and conduct a thorough post-mortem to prevent recurrence.

Quick Start

Use the incident_response skill to design an incident response process for a new service.

Frequently Asked Questions about incident_response

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

FAQPage Schema
How do I set up an incident response process for a new service?

To set up an incident response process, you need to establish clear procedures for detection, declaration, containment, and resolution of outages. This framework guides teams through operationalizing these stages to ensure swift resolution and clear stakeholder communication.

What is a blameless post-mortem and when do I need one?

A blameless post-mortem is a post-incident analysis focusing on system improvements rather than individual blame. You need one after any outage to facilitate a culture of learning from failures and prevent future recurrences.

How should our team handle outage communication with stakeholders?

Outage communication requires a structured strategy with defined cadence for internal and external status updates. This provides templates to ensure clear, consistent communication throughout the incident management lifecycle.

Does establishing a documented incident response process satisfy SOC 2 compliance requirements?

Yes, establishing a documented incident response process satisfies SOC 2 compliance requirements. It demonstrates proactive process setup, team growth, and structured outage management to auditors.

Can this incident management framework be used proactively before an outage occurs?

Yes, this incident management framework can be used proactively before an outage occurs. It supports designing and operationalizing an incident response process for new services to ensure reliability and preparedness.