Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Incident Response Plan

  • 432 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

incident-response-plan is a Claude Code skill that drafts outage and security incident runbooks covering detection, roles, communications, containment, recovery, and post-incident review for developers who need operation

About

incident-response-plan is a prompt-driven agent skill from aj-geddes/useful-ai-prompts that generates structured incident response runbooks for production outages and security events. The skill walks through detection signals, on-call roles, stakeholder communications, containment steps, recovery procedures, and post-incident review templates so SRE and backend teams can document repeatable response paths. Developers reach for incident-response-plan when launching or operating APIs and SaaS services that need documented escalation, comms channels, and rollback procedures rather than ad-hoc Slack threads during Sev-1 events. Output artifacts include role matrices, communication templates, containment checklists, and postmortem outlines suitable for Confluence, Notion, or internal wiki pages.

  • Severity tiers and on-call roles
  • Detection and escalation paths
  • Customer and stakeholder comms templates
  • Containment and rollback steps
  • Postmortem and action-item tracking

Incident Response Plan by the numbers

  • 432 all-time installs (skills.sh)
  • Ranked #532 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill incident-response-plan

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs432
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you write an incident response runbook?

Draft runbooks for outages and security events covering detection, roles, comms, containment, recovery, and post-incident review.

Who is it for?

Backend and platform engineers documenting first production incident response before or right after a major outage.

Skip if: Teams that only need automated alerting rules or PagerDuty routing without written response procedures.

When should I use this skill?

User asks for an incident response plan, outage runbook, security event playbook, or postmortem template.

What you get

Incident runbook with detection, roles, comms, containment, recovery, and postmortem sections

Files

SKILL.mdMarkdownGitHub ↗

Incident Response Plan

Table of Contents

Overview

Structured approach to detecting, responding to, containing, and recovering from security incidents with comprehensive playbooks and automation.

When to Use

  • Security breach detection
  • Data breach response
  • Malware infection
  • DDoS attacks
  • Insider threats
  • Compliance violations
  • Post-incident analysis

Quick Start

Minimal working example:

# incident_response.py
from dataclasses import dataclass, field
from typing import List, Dict, Optional
from enum import Enum
from datetime import datetime
import json

class IncidentSeverity(Enum):
    CRITICAL = "critical"  # P1 - Business critical
    HIGH = "high"          # P2 - Major impact
    MEDIUM = "medium"      # P3 - Moderate impact
    LOW = "low"            # P4 - Minor impact

class IncidentStatus(Enum):
    DETECTED = "detected"
    INVESTIGATING = "investigating"
    CONTAINED = "contained"
    ERADICATED = "eradicated"
    RECOVERED = "recovered"
    CLOSED = "closed"

class IncidentType(Enum):
    DATA_BREACH = "data_breach"
    MALWARE = "malware"
    UNAUTHORIZED_ACCESS = "unauthorized_access"
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Incident Response FrameworkIncident Response Framework
Node.js Incident Detection & ResponseNode.js Incident Detection & Response

Best Practices

✅ DO

  • Maintain incident response plan
  • Define clear escalation paths
  • Practice incident drills
  • Document all actions
  • Preserve evidence
  • Communicate transparently
  • Conduct post-incident reviews
  • Update playbooks regularly

❌ DON'T

  • Panic or rush
  • Delete evidence
  • Skip documentation
  • Work in isolation
  • Ignore lessons learned
  • Delay notifications

Related skills

How it compares

Pick incident-response-plan when you need a written operational playbook; use monitoring MCPs when you need live alerts and dashboards instead.

FAQ

What does incident-response-plan generate?

incident-response-plan generates structured incident response runbooks that cover detection, on-call roles, stakeholder communications, containment, recovery, and post-incident review. Output is ready to paste into Confluence, Notion, or an internal wiki.

When should developers use incident-response-plan?

incident-response-plan fits teams preparing for first production outages or security events on APIs and SaaS services. Use it before launch or immediately after a Sev-1 to document repeatable escalation and recovery steps.

Securitymonitoringsupport

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.