Professional incident response playbook generator based on NIST SP 800-61r3. Creates comprehensive, customized IR documentation for 11 incident scenarios including ransomware, data breach, phishing, AI/ML security, supply chain attacks, container/Kubernetes security, IoT/OT security, cloud breaches, API security, insider threats, and DDoS attacks with GDPR Article 33/34 and HIPAA breach notification guidance.
Generates comprehensive incident response playbooks based on NIST SP 800-61r3 for 11 scenarios including ransomware, data breaches, and DDoS attacks. Use when you need professional IR documentation with GDPR/HIPAA compliance guidance for your organization.
/plugin marketplace add diegocconsolini/ClaudeSkillCollection/plugin install incident-response-playbook-creator@security-compliance-marketplaceVersion: 2.2.0 Category: Security Author: Diego Consolini
This skill generates comprehensive, customized incident response playbooks based on authoritative templates from NIST SP 800-61r3 (April 2025), CISA guidance, and specialized NIST publications (SP 800-161r1, SP 800-190, SP 800-82r3, SP 800-218). It creates professional, ready-to-use playbooks for 11 different incident scenarios with built-in GDPR and HIPAA compliance considerations.
Traditional Attacks:
Modern Attack Vectors: 4. AI/ML Security Incident (High) 5. Supply Chain Attack (Critical) 6. Container/Kubernetes Security Incident (High)
Critical Infrastructure & Cloud: 7. IoT/OT Security Incident (Critical) 8. Cloud Security Breach (Critical) 9. API Security Incident (High)
Insider & Availability Threats: 10. Insider Threat (Critical) 11. DDoS Attack (High)
This skill should be activated when the user:
Example Triggers:
First, show the user what scenarios are available:
python3 scripts/browse_scenarios.py --list
This displays all available incident types with descriptions, severity levels, and compliance flags.
For detailed information about a specific scenario:
python3 scripts/browse_scenarios.py --detail ransomware
Use the AskUserQuestion tool to collect the required information from the user. This provides a beautiful, user-friendly interface for gathering customization details.
IMPORTANT: Always use AskUserQuestion for gathering this information. Do NOT just ask in text.
AskUserQuestion(questions=[
{
"question": "Which incident scenario do you need a playbook for?",
"header": "Scenario",
"multiSelect": false,
"options": [
{
"label": "Ransomware Attack",
"description": "Malware that encrypts files and demands payment for decryption. Critical severity."
},
{
"label": "Data Breach / Exfiltration",
"description": "Unauthorized access and theft of sensitive data. Critical severity with GDPR/HIPAA implications."
},
{
"label": "Phishing / BEC",
"description": "Email-based social engineering attacks to compromise credentials or conduct fraud. High severity."
}
]
}
])
AskUserQuestion(questions=[
{
"question": "What is the organization name?",
"header": "Organization",
"multiSelect": false,
"options": [
{
"label": "Provide name",
"description": "Enter the organization's name for the playbook"
}
]
},
{
"question": "What industry sector is the organization in?",
"header": "Industry",
"multiSelect": false,
"options": [
{
"label": "Healthcare",
"description": "Medical, hospitals, healthcare providers (HIPAA applicable)"
},
{
"label": "Finance",
"description": "Banks, financial services, payment processing"
},
{
"label": "Technology",
"description": "Software, SaaS, IT services"
},
{
"label": "Retail/E-commerce",
"description": "Online/offline retail, customer data"
},
{
"label": "Government",
"description": "Public sector, government agencies"
},
{
"label": "Education",
"description": "Schools, universities, educational institutions"
}
]
}
])
AskUserQuestion(questions=[
{
"question": "Do you want to customize contact information in the playbook?",
"header": "Contacts",
"multiSelect": false,
"options": [
{
"label": "Use defaults",
"description": "Use placeholder contact information (editable later)"
},
{
"label": "Provide custom",
"description": "Enter the security team email and phone number"
}
]
}
])
After collecting the information, use the generate_playbook_markdown.py script to create the playbook.
Basic Command:
python3 scripts/generate_playbook_markdown.py \
--scenario <scenario_id> \
--org "<Organization Name>" \
--industry "<Industry>"
With Custom Contact Info:
python3 scripts/generate_playbook_markdown.py \
--scenario ransomware \
--org "Acme Corporation" \
--industry "Technology" \
--contact-email "security@acmecorp.com" \
--contact-phone "+1-555-SEC-RITY" \
--output output/acme-ransomware-playbook.md
Scenario ID Mapping:
ransomwaredata_breachphishingAfter generation, complete these steps:
Example Response:
✅ Successfully generated Ransomware Attack playbook for Acme Corporation!
📄 **Output**: output/ransomware-playbook.md (7.2 KB)
The playbook includes:
- Detection indicators and monitoring guidance
- Step-by-step response procedures (Triage → Containment → Eradication)
- Recovery actions with validation checklist
- GDPR and HIPAA compliance considerations
- Communication requirements and templates
- Role-based responsibilities
- Contact information and escalation criteria
Would you like me to:
1. Display the playbook content
2. Generate a playbook for another incident type
3. Explain any section in detail
Here's a complete interaction flow:
User: "I need an incident response playbook for ransomware attacks"
Response: Let me show the ransomware scenario details first.
python3 scripts/browse_scenarios.py --detail ransomware
You: This scenario includes [summarize key points from output]
Response: I'll help generate a custom playbook. Let me gather some information about the organization.
# Use AskUserQuestion for organization name and industry
AskUserQuestion(questions=[...])
python3 scripts/generate_playbook_markdown.py \
--scenario ransomware \
--org "User's Organization" \
--industry "User's Industry"
Response: ✅ Successfully generated the ransomware playbook!
[Show file location and summary of what's included]
You: Would you like me to:
All content in generated playbooks comes from authoritative sources:
No mock or fake data - Everything is extracted from real guidance documents.
Always remind users:
Purpose: Explore available incident scenarios and view detailed information
Usage:
# List all scenarios
python3 scripts/browse_scenarios.py --list
# Show detailed view
python3 scripts/browse_scenarios.py --detail ransomware
# Display metadata
python3 scripts/browse_scenarios.py --metadata
# Search scenarios
python3 scripts/browse_scenarios.py --search "data breach"
Purpose: Generate customized incident response playbooks
Usage:
# Generate playbook with required parameters
python3 scripts/generate_playbook_markdown.py \
--scenario <scenario_id> \
--org "<Organization Name>" \
[--industry "<Industry>"] \
[--contact-email "<email>"] \
[--contact-phone "<phone>"] \
[--output "<path>"]
# List available scenarios
python3 scripts/generate_playbook_markdown.py --list
Required Parameters:
--scenario or -s: Scenario ID (ransomware, data_breach, phishing)--org or -o: Organization nameOptional Parameters:
--industry or -i: Industry sector (default: "General")--contact-email: Security team email (default: security@organization.com)--contact-phone: Security team phone (default: (555) 123-4567)--output: Output file path (default: output/[scenario]-playbook.md)Issue: "Scenario not found"
Solution: Use --list to see available scenario IDs
Issue: "Required file not found"
Solution: Ensure running from the plugin directory, or use --scenarios-file to specify path
Issue: "Invalid JSON"
Solution: The script defaults to using incident_scenarios_simplified.json which is validated
Planned features for future versions:
END OF SKILL DOCUMENTATION
For questions or issues, refer to the README.md or contact the plugin author.
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences