AGENT SKILL

incident-report

Create structured incident reports that document production incidents, impact, timeline, root cause, resolution, and follow-up actions.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 0
Forks
0

01 前言 Front Matter

name
incident-report
author
AI Business OS
license
MIT
version
1.0.0
category
template
priority
required
description
Create structured incident reports that document production incidents, impact, timeline, root cause, resolution, and follow-up actions.

03 SKILL.md 正文

Incident Report

Purpose

This skill creates comprehensive Incident Reports that document operational incidents, their business impact, response activities, root causes, and corrective actions.

Incident reports should support learning, accountability, and continuous operational improvement.


When to Use

Execute when:

  • Production incidents occur
  • Service outages happen
  • Security incidents are detected
  • Major defects impact users
  • Critical operational failures require documentation

Objectives

Produce incident reports that are:

  • Accurate
  • Timely
  • Objective
  • Actionable
  • Traceable

Inputs

Expected inputs:

  • Incident Details
  • Monitoring Alerts
  • System Logs
  • Timeline
  • Response Actions
  • Stakeholder Updates

Incident Report Structure

Generate the following sections:

  • Incident ID
  • Title
  • Severity
  • Status
  • Detection Time
  • Resolution Time
  • Duration
  • Systems Affected
  • Business Impact
  • Executive Summary
  • Timeline
  • Root Cause
  • Resolution
  • Corrective Actions
  • Preventive Actions
  • Lessons Learned
  • References

Incident Details

Document:

  • Incident Description
  • Detection Method
  • Initial Symptoms
  • Scope
  • Impacted Services
  • Customer Impact

Use factual, evidence-based descriptions.


Timeline

Include:

  • Detection
  • Escalation
  • Investigation
  • Mitigation
  • Resolution
  • Recovery
  • Closure

Record timestamps whenever possible.


Root Cause Analysis

Identify:

  • Immediate Cause
  • Contributing Factors
  • System Weaknesses
  • Human Factors
  • Process Gaps

Support conclusions with evidence.


Resolution

Describe:

  • Mitigation Steps
  • Permanent Fix
  • Validation
  • Service Restoration
  • Communication

Follow-up Actions

Assign:

  • Action Item
  • Owner
  • Priority
  • Due Date
  • Status

Track completion until closure.


Validation Checklist

Verify:

  • Timeline complete
  • Root cause validated
  • Impact documented
  • Actions assigned
  • Lessons captured
  • Stakeholders informed

Failure Conditions

Stop if:

  • Incident scope is unclear
  • Timeline is incomplete
  • Root cause is unknown
  • Evidence is insufficient
  • Action items are missing

Outputs

Generate:

  • Incident Report
  • Timeline
  • Action Register
  • Executive Summary

Rules

  • Be objective and evidence-based.
  • Avoid assigning blame.
  • Document facts chronologically.
  • Include corrective and preventive actions.
  • Maintain complete traceability.

Success Criteria

This skill succeeds when:

  • the incident is fully documented
  • root causes are understood
  • corrective actions are tracked
  • future incidents can be prevented

Related Skills

  • runbook
  • postmortem
  • devops-engineer
  • security-engineer
  • technical-writer

Version History

Version Date Description
1.0.0 2026-07-10 Initial release

04 同仓库更多 Skills