incident-response

Name: incident-response
Availability: InStock
Author: Ayub

Coordinate a four-wave incident response with three parallel agents per wave.

Updated Apr 23, 2026

Search Tags:#workflow #triage #root-cause #incident #response #incident-management

Ready to run

npx skills add https://github.com/Ayub-Khan/immortal_agent_swarm --skill incident-response-ayub-khan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/Ayub-Khan/immortal_agent_swarm/tree/main/.agents/skills/incident-response
Command: npx skills add https://github.com/Ayub-Khan/immortal_agent_swarm --skill incident-response-ayub-khan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate a rapid, structured incident response workflow to triage, identify root cause, remediate, and review post-incident findings.

Core Features & Use Cases

4-wave incident workflow with exactly three parallel sub-agents per wave to ensure redundancy and speed.
Evidence-driven analysis and durable prevention planning that translates into actionable remediation steps.
Output generation for each wave (e.g., wave_01_triage.md, wave_02_root_cause.md, wave_03_remediation.md, wave_04_post_incident.md) and final incident report.

Quick Start

Initiate the four-wave incident response workflow with exactly three parallel agents per wave to triage, identify root cause, remediate, and review.

Frequently Asked Questions about incident-response

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

FAQPage Schema

How do I coordinate incident response triage for a production outage?▼

Incident response for production outages is standardized through a four-wave workflow with three parallel agents per wave, passing memory and wave outputs between waves to triage, determine root cause, implement remediation, and document post-incident review.

What is the best way to determine root cause during a security anomaly?▼

Determining root cause for security anomalies is handled by the second wave of the incident response workflow, applying evidence-driven analysis passed from the initial triage wave to identify the underlying issue before remediation.

Can I use this incident management workflow for data integrity failures?▼

Yes, this incident management workflow applies to data integrity failures, as well as production outages, critical bugs, security anomalies, and performance degradations, enforcing a standardized four-wave response structure.

How do I document a post-incident review after remediation?▼

Post-incident review documentation is generated in the fourth wave, emitting standardized artifacts like wave_04_post_incident.md and a final incident report that translates evidence-driven analysis into actionable prevention planning.

What are the limitations of using a structured four-wave incident response?▼

The structured four-wave incident response requires exactly three parallel agents per wave and enforces a strict sequence, meaning it is designed for standardized triage and may not suit incidents requiring unstructured, ad-hoc troubleshooting outside the workflow.