skills.rest
kirvin
kirvinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

post-mortem

Analyze completed work sessions to identify friction points and propose actionable improvements.

Updated Mar 13, 2026
Search Tags:#documentation#tooling#post-mortem#workflow analysis#process improvement#lessons learned
One-click install
npx skills add https://github.com/kirvin/copilot-cli-essentials --skill post-mortem-kirvin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/kirvin/copilot-cli-essentials/tree/main/plugins/cpe/skills/post-mortem
Command: npx skills add https://github.com/kirvin/copilot-cli-essentials --skill post-mortem-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically review past work sessions, identify friction points, and propose concrete actions to improve future workflows, documentation, and tooling.

Core Features & Use Cases

  • Identify Root Causes: Digs into why issues occurred, moving beyond symptoms to systemic problems.
  • Propose Actionable Improvements: Generates specific tasks like documentation updates, code refactoring, or new skill development.
  • Use Case: After a complex debugging session that took longer than expected, use this Skill to analyze the session, pinpoint where the agent struggled, and generate a list of documentation updates and new skills needed to prevent similar issues in the future.

Quick Start

Analyze the last session to identify areas for improvement.

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I conduct a post-mortem analysis of a completed coding session?▼

A post-mortem analysis helps you systematically review past work sessions to identify friction points and propose concrete actions to improve future workflows, documentation, and tooling.

What is the best way to identify root causes of developer friction after a complex debugging session?▼

Identifying root causes requires analyzing past sessions to dig into why issues occurred, moving beyond symptoms to systemic problems like architectural clarity gaps and anti-patterns.

How do I generate actionable improvements for documentation gaps and tooling issues?▼

You generate actionable improvements by analyzing session events to pinpoint where the agent struggled, producing specific tasks like documentation updates, code refactoring, or new skill development.

Can I use workflow analysis to prevent bugs and anti-patterns in future development?▼

Yes, you can use workflow analysis to review past sessions, identifying DX friction and architectural clarity issues to propose concrete actions that prevent similar bugs and anti-patterns.

What structured input is needed to analyze session events and outcomes for process improvement?▼

You need structured input detailing specific session events and outcomes, which the analysis uses to evaluate developer experience friction, documentation gaps, and tooling inefficiencies to generate findings.

Related Skills

Explore More Software Engineering Skills→
plurigridplurigrid
60

causal-inference

Performs causal inference with structural models and Python libraries like DoWhy, CausalML, and Pyro.

Official
Advanced
xabierlameiroxabierlameiro

skill-creator

Create, modify, test, and benchmark AI skills with variance analysis.

Community
Advanced
wojonswojons
4

incident-response

Automate incident response and post-mortem analysis for system outages.

Community
Advanced
JansenAnalyticsJansenAnalytics
5

error-monitor

Monitor application logs and stderr to detect errors, crashes, and exceptions.

Community
Intermediate