incident-template

Generate incident management templates for documenting and reviewing production incidents.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill incident-template-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-template
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/operations/incident-template
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill incident-template-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams responding to production incidents often lack standardized documentation, leading to inconsistent incident reports, missed post-mortem learnings, and unclear communication during outages. This Skill generates a complete, signature-gated incident management template covering severity classification, incident reports, post-mortems, and communication templates. ## Core Features & Use Cases - Incident Report Templates: Generate structured incident reports with severity classification (SEV1-SEV4), impact assessment, timeline tracking, and resolution verification. - Post-Mortem Templates: Produce blameless post-incident review documents with root cause analysis (5 Whys), action items, and lessons learned. - Communication Templates: Create ready-to-use status page updates, internal alerts, and customer communication messages for each incident stage. - Use Case: After a production outage, use this Skill to generate the incident report and post-mortem documents, then route them to the Operations Lead for sign-off as part of Phase 12 (Operations) of the SDLC. ## Quick Start Ask the agent to generate the incident management template for your project after the ops-runbook document has been signed.

Frequently Asked Questions about incident-template

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

FAQPage Schema
How do I create an incident management template for production incidents?▼

Invoke the incident-template skill after the ops-runbook document is signed. The agent gathers your severity levels, escalation paths, and communication channels, then generates incident report, post-mortem, and communication templates at documentation/12-operations/incident-template.md.

What should a post-mortem template include?▼

A post-mortem template should include an executive summary, incident timeline, root cause analysis such as 5 Whys, what went well and poorly, action items with owners and due dates, and prevention measures. This Skill generates all of these sections automatically.

What prerequisites are required before generating incident templates?▼

The ops-runbook document must exist and be signed before this skill runs. A monitoring specification is recommended but optional. You also need team escalation contacts and severity level definitions as inputs.

Who approves the incident management template document?▼

The Operations Lead holds final approval authority and must sign the document. The DevOps Lead and CISO provide content reviews but do not gate the signature.

How are incident severity levels classified?▼

The template defines four severity levels: SEV1 for critical outages with 15-minute response, SEV2 for major degradation with 30-minute response, SEV3 for minor issues with 2-hour response, and SEV4 for low-impact issues handled next business day.