incident

Manage production incident response from triage through post-incident review.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill incident-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/incident
Command: npx skills add https://github.com/lalulali/vespyr --skill incident-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured response when production systems break, helping teams reduce user impact quickly, investigate causes calmly, and prevent the issue from happening again.

Core Features & Use Cases

  • Incident Triage: Classify severity, assign responders, and open the incident workspace.
  • Mitigation and Recovery: Roll back, disable features, scale services, and communicate status before deep debugging.
  • Root-Cause Analysis and Follow-Up: Document the timeline, identify contributing factors, add fixes and tests, and produce a blameless post-incident review.
  • Use Case: A payment API starts failing in production and customers cannot check out; this Skill guides the team from urgent mitigation through RCA, remediation, and lessons learned.

Quick Start

Use the incident skill to triage this production outage, reduce user impact, and produce the incident artifacts for root-cause analysis and postmortem review.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I handle a production outage and reduce user impact quickly?

Handle a production outage by triaging severity, assigning responders, and prioritizing mitigation like rolling back or scaling services before deep debugging. This structured incident response reduces user impact quickly and safely.

What is a blameless postmortem and when do I need one for incident response?

A blameless postmortem is a post-incident review documenting the timeline and contributing factors without assigning fault. You need one after incident mitigation to identify root causes and produce follow-up prevention actions.

How do I conduct root cause analysis for a production error spike?

Conduct root cause analysis for an error spike by documenting the incident timeline, identifying contributing factors, and adding fixes with tests. This process transitions from urgent mitigation into structured remediation and review.

Can I use this incident response process for data integrity failures and SLA-impacting degradation?

Yes, this incident response process applies to data integrity failures, security incidents, and SLA-impacting performance degradation. It scales severity-based escalation and coordinated artifact tracking across various production failure types.

What is the best way to triage a production service failure?

The best way to triage a production service failure is to classify severity, assign responders, and open an incident workspace immediately. Triage establishes coordinated artifact tracking for the entire response lifecycle.

Does incident response require specific dependencies to manage mitigation and remediation?

No external dependencies are required to manage mitigation and remediation. The incident response process relies on severity-based escalation and coordinated artifact tracking to guide teams from triage through blameless documentation.