postmortem

Name: postmortem
Availability: InStock
Author: slavochek2

Identify and summarize post-mortem evidence from P-number feature delivery.

1|Updated Nov 26, 2025

Search Tags:#documentation #postmortem #ai-automation #root-cause-analysis #quality-improvement #pipeline-analysis

Ready to run

npx skills add https://github.com/slavochek2/claritypledge --skill postmortem-slavochek2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/slavochek2/claritypledge/tree/main/.claude/commands/slava/maintain/postmortem
Command: npx skills add https://github.com/slavochek2/claritypledge --skill postmortem-slavochek2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortem analysis of a shipped feature — identifies what broke in the delivery pipeline and proposes concrete improvements to prevent recurrence.

Core Features & Use Cases

Gather evidence from specs, commit history, and branch activity to surface root-cause categories.
Propose concrete, maintainable pipeline improvements and track them as initiatives.
Generate a structured post-mortem report for decision records (docs/decisions).

Quick Start

Trigger a P-number postmortem by loading the feature context and following Steps 1 through 5.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I run a post-mortem analysis on a shipped feature to identify pipeline issues?▼

Run a post-mortem by loading feature context including commit histories, spec statuses, and process documents. The analysis categorizes identified issues into predefined gap categories and proposes concrete pipeline improvements to prevent recurrence.

What evidence do I need to perform a root-cause analysis on feature delivery?▼

Root-cause analysis requires access to commit histories, spec statuses, and process documents. This evidence is gathered and summarized to surface workflow gaps, detecting a minimum of 3 fix-category issues for actionable initiatives.

Can I use this post-mortem process for multiple features at once?▼

No, this post-mortem process applies to single-feature post-mortems within the ClarityPledge pipeline. It is designed to analyze evidence from one P-number feature delivery at a time to accurately surface workflow gaps.

How does post-mortem documentation improve quality in a delivery pipeline?▼

Post-mortem documentation improves quality by categorizing workflow gaps from spec and commit history evidence into predefined categories. It then generates a structured report proposing concrete, maintainable pipeline improvements tracked as initiatives.

What is the best way to document root-cause findings from a post-mortem?▼

The best way to document root-cause findings is by generating a structured post-mortem report for decision records in docs/decisions. This report surfaces categorized issues and proposes concrete initiatives to fix delivery pipelines.

Why does the post-mortem analysis require 3 or more fix-category issues?▼

The post-mortem analysis requires detecting 3 or more fix-category issues to ensure sufficient evidence depth. This threshold guarantees that proposed improvements are based on meaningful workflow gaps rather than isolated incidents.