incident

Coordinate structured incident response for production outages with triage, containment, and postmortem workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It guides AI assistants through disciplined incident response so outages are triaged quickly, contained safely, and documented consistently instead of being debugged ad hoc.

Core Features & Use Cases

  • Severity Triage: Classifies incidents as P1, P2, or P3 based on impact and containment urgency.
  • Containment First: Forces rollback, feature-flag, traffic-shift, or other mitigation before any root-cause work.
  • Verification and Security Checks: Uses watchdog verification and guardian review to confirm stability and assess exposure risks.
  • Timeline and Postmortem Output: Produces a complete incident timeline, journal entry, and postmortem with prevention actions.
  • Use Case: A production deploy breaks login for part of the user base, and this Skill helps the agent stabilize service, confirm recovery, and write the incident report.

Quick Start

Ask the assistant to respond to a production incident by triaging severity, containing the blast radius, verifying stability, checking for security impact, and drafting the postmortem.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I run a structured incident response for a production outage?

Structured incident response requires triaging severity, containing the blast radius before root cause analysis, verifying stability, checking security exposure, and drafting a postmortem with prevention actions.

What is the proper triage process for production reliability incidents?

Triage classifies incidents as P1, P2, or P3 based on user impact and containment urgency, establishing severity before any mitigation or root cause analysis begins.

How do I contain a degraded service before performing root cause analysis?

Containment forces rollback, feature-flag toggles, or traffic-shift mitigations to stabilize the degraded service before any debugging or root cause analysis work starts.

Can I automate postmortem artifact generation after an outage?

Postmortem artifact generation produces a complete incident timeline, journal entry, and postmortem document with prevention actions after watchdog verification confirms service stability.

Does incident response workflow require security review during an outage?

Incident response includes guardian security checks to assess exposure risks alongside watchdog verification, ensuring stability confirmation and security review happen before final postmortem generation.

What's the best way to document an incident timeline for production reliability?

Documenting an incident timeline uses journal logging throughout the response workflow, capturing triage, containment, verification, and security review steps to produce a complete postmortem artifact.