incident-readiness

Evaluate monitoring, SLO/SLI alignment, and runbook coverage for AWS-backed services.

6|1|Updated Mar 30, 2026

Search Tags:#production readiness #incident response #on-call #runbooks #cloudwatch #slo sli #aws fis

Ready to run

npx skills add https://github.com/wesleyosantos91/multi-agents --skill incident-readiness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-readiness
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/incident-readiness
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill incident-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident-readiness evaluations prevent surprises during production incidents by checking whether your system’s monitoring, SLO/SLI definitions, runbooks, and response processes are actually in place.

Core Features & Use Cases

Operational readiness assessment: checks SLOs/SLIs per critical component and verifies they map to real AWS metrics.
Detection and escalation coverage: confirms CloudWatch alarms exist for SLO breaches and that runbooks are available for each critical alarm.
Response process completeness: verifies postmortem templates, on-call and escalation documentation, and defined error budgets, including whether chaos engineering via AWS FIS is considered.
Scope control: targets either the full system or a specific component based on the provided argument.

Quick Start

Ask an AI to run incident-readiness for a specific component by providing its name as the skill argument.

Frequently Asked Questions about incident-readiness

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

FAQPage Schema

How do I check if my production system is ready for an incident?▼

Production incident readiness is checked by evaluating monitoring, SLO/SLI alignment, runbook coverage, and escalation processes. This ensures SLOs are defined per critical component and mapped to real CloudWatch metrics to prevent surprises during outages.

How do I validate that my CloudWatch alarms cover SLO breaches?▼

Validating SLO breach coverage requires confirming CloudWatch alarms exist for each defined SLO. The process checks that alarms map to real AWS metrics and verifies operational runbooks are available for every critical alarm triggered.

What is needed for a complete incident response process in AWS?▼

A complete incident response process requires postmortem templates, on-call and escalation documentation, and defined error budgets. It also involves checking whether chaos engineering consideration via AWS FIS is integrated into your preparedness reviews.

Can I assess incident readiness for just one specific component?▼

Yes, incident readiness can target either the full system or a specific component. You provide the component name as an argument to scope the operational readiness assessment to that particular service.

Why do I need runbooks for my CloudWatch alarms?▼

Runbooks are needed for CloudWatch alarms to ensure detection and escalation coverage. They provide documented response procedures for each critical alarm, preventing unstructured reactions when SLO breaches occur in production.