Verified:GitHub

conducting-postmortem

Analyze debugging sessions to identify systemic failures and update using-* skills.

Updated Jan 20, 2026

Search Tags:#retrospective #post-mortem #knowledge-management #root-cause-analysis #process-improvement #skill-evolution

Ready to run

npx skills add https://github.com/Alanlee0323/my-agent-skills --skill conducting-postmortem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conducting-postmortem
Source: https://github.com/Alanlee0323/my-agent-skills/tree/main/conducting-postmortem
Command: npx skills add https://github.com/Alanlee0323/my-agent-skills --skill conducting-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies root causes from debugging sessions and project retrospectives and translates them into preventive guardrails by updating the relevant using-* skills.

Core Features & Use Cases

RCA (root-cause analysis) of recurring failures across debugging and project work
Gap analysis of existing using-* SKILLs to identify missing guardrails
Proactive skill evolution by updating SKILL.md to prevent recurrence

Quick Start

Analyze the latest debugging session and project retrospective to draft and apply an optimization update to the relevant using-* skill.

Frequently Asked Questions about conducting-postmortem

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

FAQPage Schema

How do I identify systemic failures from debugging logs to prevent recurring errors?▼

Conduct a root-cause analysis on debugging logs and project retrospectives to identify recurring error patterns, then document gap analyses and optimization proposals directly in SKILL.md to prevent recurrence.

What is the best way to run a root-cause analysis on a project retrospective?▼

The best way to run a root-cause analysis on a project retrospective is to analyze interaction history and debugging outcomes to identify systemic failures, then update relevant using-* skills with preventive guardrails.

How do I update skill documentation to add preventive guardrails after debugging?▼

Update skill documentation by editing SKILL.md to document root-cause analyses, gap analyses, and optimization proposals derived from debugging sessions, establishing preventive guardrails against recurring failures.

Can I use this skill to perform gap analysis on existing using-* skills?▼

Yes, you can use this skill to perform gap analysis on existing using-* skills by evaluating project outcomes and debugging sessions to identify missing guardrails and implement proactive skill evolution.

Do I need access to debugging logs to document root-cause analyses?▼

Yes, you need access to debugging logs and interaction history to accurately document root-cause analyses, as this skill requires historical session data to identify recurring error patterns and update skills.