skills.rest
wizeline
wizelineOFFICIAL
Explore all skills by this author →
WebsiteGitHub

incident-documenting

Generate incident documentation artifacts including escalation briefs, Jira tickets, and postmortem drafts.

Updated Aug 27, 2026
Search Tags:#documentation#communication#postmortem#escalation#incident management#jira ticket
One-click install
npx skills add https://github.com/wizeline/sdlc-agents --skill incident-documenting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-documenting
Source: https://github.com/wizeline/sdlc-agents/tree/main/aicores/incident-resolution-agent/skills/incident-documenting
Command: npx skills add https://github.com/wizeline/sdlc-agents --skill incident-documenting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of essential incident documentation artifacts, streamlining communication and record-keeping during and after critical events.

Core Features & Use Cases

  • Escalation Briefs: Quickly generate concise briefs for escalating incidents to other teams or management.
  • Jira Tickets: Draft detailed Jira tickets with root cause, timeline, and resolution steps.
  • Postmortem Drafts: Create comprehensive postmortem documents for blameless learning and prevention.
  • Incident Summaries: Produce clear, asynchronous updates for stakeholders.
  • Use Case: After resolving a P1 incident, use this skill to immediately draft a Jira ticket and a postmortem outline, ensuring all critical details are captured while fresh.

Quick Start

Use the incident-documenting skill to draft the Jira ticket for the current incident.

Frequently Asked Questions about incident-documenting

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

FAQPage Schema
How do I generate an incident postmortem draft from a resolved P1 issue?▼

You can generate a Jira ticket by providing the incident details to automatically draft the root cause, timeline, and resolution steps. It outputs markdown files structured for direct pasting into Jira or PagerDuty.

What is the best way to document an incident escalation brief for management?▼

The best way to document an incident escalation brief is to use automated generation tools that produce concise summaries from incident inputs. This ensures strict output formatting and content completeness for effective communication.

Does this incident documentation approach support exporting to Confluence and PagerDuty?▼

Yes, the incident documentation approach supports automated saving of markdown files designed for direct use in Confluence and PagerDuty. This allows seamless integration into existing incident management workflows.

Can I create an incident timeline summary for asynchronous stakeholder updates?▼

Yes, you can create an incident timeline summary to produce clear, asynchronous updates for stakeholders. The generated markdown artifacts capture critical details while they are fresh after resolution.

Related Skills

Explore More Software Engineering Skills→
kid-sidkid-sid
186

incident-response

Triage production alerts, coordinate response, and document post-incident learnings.

Community
Advanced
cyperx84cyperx84
2

Incident Response

Guide structured incident response from alert detection to post-mortem.

Community
Basic
RambleRainbowRambleRainbow

videodb

Upload videos, search content semantically, and edit timelines server-side.

Community
Advanced
cafe3310cafe3310
248

doc-template-provider

Generate standardized project and product documentation from reusable markdown templates.

Community
Basic