Incident Response Plan

Develop comprehensive incident response plans with clear roles, procedures, communication protocols, and recovery workflows. Use when establishing IR processes, conducting tabletops, or updating response procedures after incidents.

48 stars 10 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill incident-response-plan
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/incident-response/skills/incident-response-plan ~/.claude/skills/incident-response-plan

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Incident Response Planning

Build a comprehensive incident response program with clear roles, procedures, severity classifications, and communication protocols to minimize mean time to detection (MTTD) and mean time to resolution (MTTR).

## Context

You are building or improving an incident response (IR) program. A strong IR program doesn't prevent all incidents, but it dramatically reduces their impact. Organizations without plans suffer: longer detection time, chaotic response, poor communication, and higher customer impact. An effective plan is practiced, documented, and clear on roles.

IR is not a one-time document; it's a living program that improves after each incident through post-mortems and tabletop exercises.

## Domain Context

- **Incident Categories**: Malware, phishing, data breach, ransomware, DDoS, account compromise, insider threat, supply chain attack, compliance violation
- **Response Phases**: Detection → Triage → Containment → Investigation → Recovery → Post-Incident Review
- **Incident Classification**: Severity (Critical, High, Medium, Low) drives response speed and escalation
- **MTTD (Mean Time to Detect)**: How quickly is an incident discovered? Goal: <1 hour for critical
- **MTTR (Mean Time to Resolve)**: How quickly is an incident resolved? Goal: <4 hours for critical
- **Communication**: Incident commander coordinates response; clear escalation ensures executive/customer awareness
Read the full skill on GitHub

Details

Skill name
incident-response-plan
Path
security/incident-response/skills/incident-response-plan/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Incident Response Plan skill do?

Develop comprehensive incident response plans with clear roles, procedures, communication protocols, and recovery workflows. Use when establishing IR processes, conducting tabletops, or updating response procedures after incidents.

How do I install the Incident Response Plan skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Incident Response Plan popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.