postmortem

Reviews completed activities step by step to extract and persist lessons learned.

3|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/isizono/calm --skill postmortem-isizono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/isizono/calm/tree/main/skills/postmortem
Command: npx skills add https://github.com/isizono/calm --skill postmortem-isizono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a task, valuable insights about what worked and what went wrong are often lost. This Skill guides a structured retrospective over a completed activity, turning discussion logs and decisions into durable lessons. ## Core Features & Use Cases - Step-by-step review: Decomposes a completed activity's logs into chronological steps and reviews each one interactively with the user. - Reflection summary: Compiles what went well and what to improve, saved as a material attached to a dedicated postmortem activity. - Lesson persistence: Helps decide where to store actionable lessons, such as tag notes, decisions, auto memory feedback, or CLAUDE.md rules. - Use Case: After completing a multi-session refactoring task, run a postmortem to walk through each step, identify why a wrong design choice was made, and persist a rule so the same mistake is not repeated. ## Quick Start Ask the AI to run a postmortem on the activity you just finished, for example by saying "let's do a retrospective on this work".

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I run a postmortem on a completed activity?▼

Invoke the skill with an activity_id argument, or let it list up to 15 completed activities via get_activities so you can pick one. It then creates a dedicated retrospective activity and walks through each step interactively.

What data does a retrospective review use?▼

The review collects logs and decisions tied to related topics, explores linked entities with get_map, and checks stored materials. If logs and decisions are too sparse, it asks you to narrate what happened to build the steps manually.

Where are lessons learned stored after a retrospective?▼

Lessons can be persisted as tag notes, topic decisions, Claude Code auto memory feedback, CLAUDE.md project rules, or new intent tags. The skill presents the options, but you decide where each lesson goes.

Can a postmortem span multiple sessions?▼

Yes. Progress is logged frequently during the review, so the retrospective can pause and resume across sessions without losing context, since all records live in the persistent memory database.

When should I not use this postmortem skill?▼

Do not use it for simply marking an activity complete or syncing memory records; those are handled by activity-finish and sync-memory. It is designed only for reflective review of already completed work.