skills.rest
Sounder25
Sounder25COMMUNITY
Explore all skills by this author →
GitHub

Failure Postmortem

Log structured failure data to a central postmortem registry.

27|8|Updated Jan 16, 2026
Search Tags:#PowerShell#postmortem#root-cause#forensics#incident-management#log-failure
One-click install
npx skills add https://github.com/Sounder25/Google-Antigravity-Skills-Library --skill failure-postmortem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Failure Postmortem
Source: https://github.com/Sounder25/Google-Antigravity-Skills-Library/tree/main/20_failure_postmortem
Command: npx skills add https://github.com/Sounder25/Google-Antigravity-Skills-Library --skill failure-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill captures failure data and logs it to a persistent registry for formal analysis of root causes and preventive rules.

Core Features & Use Cases

  • Centralized logging: appends structured postmortem entries to a central registry (POSTMORTEMS.md) for auditability and learning.
  • Trigger & inputs: supports common failure signals (log failure, postmortem, why did this fail, record error) with clear input parameters.
  • Integrated workflow: provides a guided analysis path to document root cause and preventive actions, enabling reliable incident learning.

Quick Start

Run the PowerShell script to log a failure example: execute the script with -Command "deploy" -Error "Out of memory" -Context "Deployment" to create a new postmortem entry.

Frequently Asked Questions about Failure Postmortem

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

FAQPage Schema
How do I log failure data for a root-cause analysis and postmortem?▼

To log failure data for root-cause analysis, execute the PowerShell script with command, error, and context parameters to append a structured postmortem entry to a central registry.

What is the best way to document an incident postmortem to prevent recurrence?▼

Documenting an incident postmortem requires capturing failure data and logging it to a persistent registry, which enforces structured inputs and supports guided preventive-rule documentation to prevent recurrence.

Can I use PowerShell to record forensic data when an automation tool fails?▼

Yes, you can use the PowerShell script to record forensic data during tool failures by supplying the failed command, error message, and context to log the event for postmortem analysis.

Does this postmortem logging approach support abandoned plans across automation workflows?▼

Yes, this postmortem logging approach applies during tool failures and abandoned plans across automation workflows, capturing the necessary data for formal incident investigations and forensic analysis.

Why do I need structured inputs for logging a postmortem entry?▼

Structured inputs are required for logging a postmortem entry to ensure the failure data is consistent, enabling reliable incident learning, guided root-cause analysis, and auditability in the central registry.

Related Skills

Explore More Software Engineering Skills→
yt3treesyt3trees

powershell-quality

Generate PowerShell scripts with headers, Shift_JIS encoding, error handling, and SQL Server patterns for GRANDIT ERP.

Community
Intermediate
zineyuzineyu

trellis-break-loop

Analyze bug fixes to identify root causes and prevention strategies.

Community
Advanced
sfinessfines

bmad-investigate

Automate forensic case investigation by grading evidence and managing case files.

Community
Advanced
MotWakorbMotWakorb
2

postmortem

Guide teams through blameless incident postmortems with evidence-based root-cause analysis.

Community
Advanced