conducting-postmortem

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.

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.

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.

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.

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.