ywc-incident-postmortem

Name: ywc-incident-postmortem
Availability: InStock
Author: yongwoon

Generate structured incident postmortems with timeline reconstruction and 5 Whys analysis.

8|1|Updated May 13, 2026

Search Tags:#documentation #root cause #security #reliability #postmortem #incident

Ready to run

npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-incident-postmortem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ywc-incident-postmortem
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-incident-postmortem
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-incident-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This skill addresses the lack of structured documentation following production incidents, ensuring that teams capture critical learnings, perform root cause analysis, and define actionable prevention steps before memory fades.

Core Features & Use Cases

Structured Analysis: Guides the user through timeline reconstruction, 5 Whys root cause analysis, and impact assessment.
Security Integration: Automatically dispatches security advisors when incidents involve auth bypass, data leaks, or OWASP-related vulnerabilities.
Client Communication: Generates sanitized, professional reports for external stakeholders while keeping internal technical details private.
Use Case: After a service outage, use this skill to generate a comprehensive internal report and a client-facing summary to maintain transparency and prevent recurrence.

Quick Start

Trigger the ywc-incident-postmortem skill to begin an interactive session for documenting the recent production incident.

Frequently Asked Questions about ywc-incident-postmortem

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

FAQPage Schema

How do I generate a structured incident postmortem after a production outage?▼

Incident postmortem generation reconstructs the timeline, performs 5 Whys root cause analysis, and defines prevention action items to capture critical learnings after a production outage before memory fades.

What is the best way to document root cause analysis for a security incident?▼

Root cause analysis for a security incident is handled by dispatching security advisors automatically when auth bypass, data leaks, or OWASP vulnerabilities are detected, ensuring specialized investigation for the report.

Can I create a sanitized client-facing incident report without exposing internal technical details?▼

Sanitized client-facing incident reports are generated automatically, providing professional external stakeholder communication while keeping internal technical details and root cause analysis private.

Does the postmortem process require specific environment setup or dependencies?▼

Generating incident postmortems requires the gh dependency for integration and benefits from incident context to accurately reconstruct the timeline and assess impact.

When do I need to use the 5 Whys technique for incident documentation?▼

The 5 Whys technique is needed during incident documentation to systematically identify the underlying root cause of production outages or security incidents, ensuring actionable prevention steps are defined.

What are the limitations of using automated postmortem generation for reliability reporting?▼

Automated postmortem generation relies on provided incident context to reconstruct timelines and define prevention action items, meaning incomplete input data will limit the accuracy of the root cause analysis.