incident-response

Manage incident response workflows for production outages and alerts.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/FoundationForge/cowork-plugins --skill incident-response-foundationforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/engineering/skills/incident-response
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill incident-response-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage incidents efficiently by guiding teams through triage, communication, mitigation, and postmortem documentation to reduce downtime and ensure clear, factual updates during outages.

Core Features & Use Cases

  • Structured Triage: Assess severity (SEV1-4), identify impacted systems and assign roles (IC, comms, responders).
  • Communication Templates: Generate internal status updates and customer-facing messages and advise on cadence and war room setup.
  • Postmortem Generation: Produce blameless postmortems with timelines, root cause analysis (5 whys), action items, and owners.
  • Use Case: An on-call engineer facing a production outage can start a new incident, post ongoing status updates to the incident channel, and generate a complete postmortem after resolution.

Quick Start

Start a new incident by running /incident-response new with a brief description of the alert or outage.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I manage incident response for production outages and alerts?

Incident response management guides on-call engineers and incident commanders through triage, communication, mitigation, and blameless postmortem documentation to reduce downtime during production outages.

How do I generate a blameless postmortem after resolving an incident?

Blameless postmortem generation produces documentation featuring incident timelines, root cause analysis using the 5 whys methodology, assigned action items, and identified owners after resolution.

What is the best way to structure triage for a SEV1 production outage?

Structured triage assesses incident severity levels from SEV1 to SEV4, identifies impacted systems, and assigns specific incident response roles including incident commander, communications lead, and responders.

How do I write status updates for customers during an active incident?

Communication templates generate both internal status updates and customer-facing messages while advising on appropriate update cadence and war room setup during active incidents.

Can I integrate incident management with monitoring and chat connectors?

Incident management integrates with monitoring, incident management, and chat connectors to pull alerts, create incidents, and post ongoing status updates to the incident channel.

Do I need a concise incident description to start an incident response workflow?

A concise incident description is required to start an incident response workflow, allowing the system to process the alert or outage and begin the triage and mitigation phases.