incident-cycle

Coordinate incident workflows from diagnosis through retrospective with root-cause analysis.

Updated Mar 26, 2026

Search Tags:#devops #retrospective #postmortem #root-cause-analysis #incident #incident-management

Ready to run

npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill incident-cycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-cycle
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/incident-cycle
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill incident-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident management often lacks a structured, repeatable process from detection to prevention, causing prolonged outages and repeated mistakes.

Core Features & Use Cases

End-to-end incident workflow: diagnosis, planning, implementation, testing, deployment, and retrospective.
Post-incident learning: root-cause analysis and preventative actions to reduce recurrence.
Collaboration-ready: guides teams through documentation and sign-offs during post-mortems.

Quick Start

Describe an incident and ask the AI to outline and execute the full incident-cycle workflow from diagnosis to retrospective.

Frequently Asked Questions about incident-cycle

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

FAQPage Schema

How do I structure incident management from detection to prevention?▼

Incident management requires a structured workflow covering diagnosis, planning, implementation, testing, deployment, and retrospective to reduce MTTR and prevent recurrence. This coordinates end-to-end operational incident response.

What is the best way to conduct a root-cause analysis after an outage?▼

Root-cause analysis during a post-mortem identifies underlying factors and generates preventative actions. Applying structured retrospective steps ensures collaboration-ready documentation and sign-offs to prevent repeated mistakes.

Can I use a structured workflow to reduce MTTR for operational incidents?▼

Yes, applying a structured incident workflow with clear steps and guardrails across diagnosis, validation, and deployment reduces MTTR. It enforces repeatable processes from detection through post-incident learning.

How do I facilitate a post-mortem with documentation and team sign-offs?▼

Facilitate post-mortems by guiding teams through structured documentation and sign-offs during the retrospective phase. This collaboration-ready approach ensures accountability and drives preventative actions.

Does incident-cycle work for recurring operational incidents without a repeatable process?▼

Yes, it applies to operational incidents lacking a repeatable process by enforcing a structured workflow. It covers end-to-end incident management from detection through retrospective to prevent prolonged outages.

What steps do I need to execute an end-to-end incident workflow?▼

Describe an incident and outline the full workflow from diagnosis to retrospective. Execute structured steps including change planning, validation, testing, deployment, and post-mortem learning to achieve lasting fixes.