incident-triage

Guide incident responders through structured triage with severity levels and postmortem templates.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/vib795/copilot-anatomy --skill incident-triage-vib795
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-triage
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/incident-triage
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill incident-triage-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a structured, repeatable process for incident triage, ensuring consistent assessment, documentation, and escalation during outages.

Core Features & Use Cases

  • Structured severity levels and triage checklist to rapidly assess impact across services.
  • Timeline capture format to maintain an auditable incident log.
  • Postmortem template to guide root-cause analysis and action items.

Quick Start

Follow the triage checklist in this guide to establish impact, verify dashboards, and begin timeline capture for an incident.

Frequently Asked Questions about incident-triage

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

FAQPage Schema
What is structured incident triage and when do I need it for production outages?

Structured incident triage provides a repeatable process for assessing impact, documenting timelines, and escalating during production outages. You need it when managing multi-service incidents to ensure consistent, auditable responses across your on-call team.

How do I run an incident triage workflow across multi-service environments?

To run incident triage, follow a standardized checklist to establish impact, verify dashboards, and begin timeline capture. The workflow includes defined roles and severity levels to rapidly assess damage and coordinate response across affected services.

How do I capture an auditable incident timeline during an active outage?

Capture an auditable incident timeline using a dedicated timeline format that logs events as they happen during an outage. This maintains a chronological record of responder actions, system changes, and discoveries for later review.

What's the best way to write a postmortem after an incident is resolved?

The best way to write a postmortem is using a reusable template that guides root-cause analysis and tracks action items. This ensures your post-incident review captures the underlying issues and preventative steps consistently.

Can I use a standardized severity model for degraded performance incidents?

Yes, you can use a standardized severity model to assess degraded performance incidents. The triage process includes defined severity levels that help responders quickly classify and respond to outages, slow performance, and partial degradations.

Does structured incident triage work without dedicated incident management software?

Structured incident triage works independently as a guided workflow with built-in guardrails like checklists and templates. It provides the process framework for assessment and documentation, functioning without requiring specific external incident management dependencies.