postmortem

Analyze failed events and produce structured post-mortems with root causes and corrective actions.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill postmortem-veloxia-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/Veloxia-agency/VELOXIA-WEB/tree/main/.claude/skills/c-level-advisor/executive-mentor/skills/postmortem
Command: npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill postmortem-veloxia-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and leaders analyze failures without blame so they can understand what actually happened, why it happened, and how to prevent it from recurring.

Core Features & Use Cases

  • Rigorous failure analysis: Breaks incidents into expected vs. actual outcomes, timeline, impact, and root causes.
  • Systemic learning: Separates contributing factors from root causes and surfaces warning signs that were missed.
  • Actionable follow-through: Converts findings into owned, dated changes with a verification date so improvements actually stick.
  • Use case: Review a missed quarter, a failed deal, a bad hire, or a product launch that underperformed and produce a structured post-mortem that leads to specific next steps.

Quick Start

Use the postmortem skill to analyze this failed event and produce a structured post-mortem with root causes, missed warning signs, ownership, and verification dates.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I conduct a root cause analysis for a failed product launch?

Root cause analysis for a failed product launch involves reconstructing the event timeline, separating contributing factors from actual root causes, and reviewing missed warning signs. This process produces a structured post-mortem with owned, dated corrective actions to prevent recurrence.

What is the best way to run a blameless retrospective after a missed sales quarter?

A blameless retrospective for a missed sales quarter analyzes expected versus actual outcomes and assesses existing controls. It converts systemic findings into an action plan with assigned owners, due dates, and a verification schedule to ensure the missed quarter does not repeat.

When do I need a formal failure review for operational incidents?

You need a formal failure review for operational incidents when a timeline reconstruction, warning-sign review, and control assessment are required to understand what happened. It is necessary to establish a change register that guarantees corrective actions are tracked and verified.

Can I use the five whys technique to analyze a bad hiring decision?

Yes, applying the five whys technique to a bad hire helps drill down past contributing factors to the systemic root cause. The analysis generates a structured post-mortem with specific corrective actions, ownership assignments, and verification dates to improve your hiring process.

Does this postmortem process assign owners and due dates for corrective actions?

Yes, the postmortem process mandates a change register that converts findings into owned, dated changes. It requires explicit owner assignments, due dates, and verification planning to ensure that corrective actions are implemented and recurrence is actively prevented.

What limitations exist when analyzing complex business failures with multiple contributing factors?

When analyzing complex business failures, a limitation is distinguishing true root causes from overlapping contributing factors without assigning blame. The process requires rigorous control assessment and a strict change register; without accurate owner assignments and verification dates, corrective actions may fail to prevent recurrence.