What is the purpose of the /em:postmortem command?

The command initiates a structured, C-level style analysis of a specific event or failure to extract maximum learning value and prevent recurrence.

What is a Change Register?

A Change Register is the final output of the post-mortem, listing specific, owned, and dated commitments to change processes or systems based on the findings.

Can this be used for technical incidents?

Yes, while designed with an executive lens, it is highly effective for technical outages, security breaches, or failed deployments where systemic process changes are required.

What is the 5 Whys technique used in this skill?

It is an iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem by repeating the question 'Why?' five times.

How does this skill help avoid a blame-based culture?

It focuses on the 'systemic conditions' that made an outcome predictable rather than scapegoating individuals, shifting the focus to process improvement.

C-Level Post-Mortem Advisor

Name: C-Level Post-Mortem Advisor
Author: oabdelmaksoud

byoabdelmaksoud

0•

コラボレーションツール

Conducts rigorous, blameless post-mortem analyses to identify root causes and systemic improvements following project or organizational failures.

This skill acts as a high-level executive mentor, guiding users through a structured framework to analyze failures like missed targets, failed product launches, or unsuccessful hires. Unlike standard retrospectives that often result in blame or vague action items, this tool focuses on systemic investigation. It employs a deep '5 Whys' approach to separate symptoms from root causes, identifies ignored warning signs, and distinguishes between controllable and uncontrollable factors. The process concludes with a concrete Change Register that assigns specific ownership and verification dates to ensure lasting organizational growth.

主な機能

010 GitHub stars

02Analysis of ignored early warning signs and psychological safety barriers.

03Standardized Change Register output with owners, dates, and verification steps.

04Clear distinction between internal controllable actions and external market factors.

05Categorization of contributing factors versus fundamental root causes.

06Structured '5 Whys' framework to uncover deep systemic root causes.

ユースケース

01Analyzing missed quarterly revenue targets to identify gaps in sales qualification processes.

02Investigating a failed product feature launch to refine market-fit discovery cycles.

03Reviewing unsuccessful high-level hires to improve organizational competency frameworks.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add oabdelmaksoud/superclaw postmortem

For use in Claude.ai and ChatGPT