AI Skills Catalog
AI Workers

Post Mortem

Evaluate a completed strategic decision against its original success and kill criteria. Compare actual outcomes, revisit recorded dissent and assumptions, and write a post-mortem with process lessons and specific forward actions.
SKILL SCORE80How it is scored
VerifiedFreeMIT

Works with

Packaged from the source skill for Claude, Codex and 4 more.

Workflow

Evaluate a completed strategic decision against its original success and kill criteria. Compare actual outcomes, revisit recorded dissent and assumptions, and write a post-mortem with process lessons and specific forward actions.

Requirements and limits

Needs the original decision and execution records; absent precommitted criteria should be identified instead of retrofitted to the outcome.

What is inside the skill

Section headings from the original SKILL.md (about 231 words of instructions). Read the full text in the source repository before installing.

  1. Pipeline Position
  2. When to Run
  3. Inputs
  4. Output: Post-Mortem Record
  5. Why Pre-Committed Criteria Matter
  6. Why Revisit Dissent
  7. Routing
  8. Related

Bundled files

  • LICENSE

Example prompts

  • Review our market-expansion decision against the metrics we committed to 90 days ago.
  • Revisit dissent from the boardroom memo after our pricing change underperformed.

How to install Post Mortem

Claude Packaged
  1. Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
  2. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
  3. For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
  4. Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
More about skills for Claude
Codex Packaged
  1. Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
  2. Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
  3. Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
  4. AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
More about skills for Codex
GPT Packaged
  1. Download the GPT package from the skill page.
  2. Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
  3. Upload the bundled reference files as knowledge so the GPT can consult them.
  4. Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
More about skills for GPT
Gemini Packaged
  1. Download the Gemini package from the skill page.
  2. For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
  3. Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
  4. Test a matching task and verify the referenced tools and files are available.
More about skills for Gemini
Cursor Packaged
  1. Download the Cursor package from the skill page.
  2. Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
  3. Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
  4. Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
More about skills for Cursor
OpenCode Packaged
  1. Download the OpenCode package from the skill page.
  2. Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
  3. Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
  4. Start OpenCode in the project and test a matching task with the model and permissions you use.
More about skills for OpenCode

Permissions & security

Low risk

Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method

Read project files
Write generated skill files

Post Mortem FAQ

What does the Post Mortem skill do?

Evaluate a completed strategic decision against its original success and kill criteria. Compare actual outcomes, revisit recorded dissent and assumptions, and write a post-mortem with process lessons and specific forward actions.

Which AI agents can use Post Mortem?

Packages for Claude, Codex and 4 more are built from the same source instructions.

How do I install Post Mortem in Claude?

Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.

Who made Post Mortem and what is the license?

Post Mortem is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/post-mortem. The catalog keeps the original attribution.

What permissions does Post Mortem need?

Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.

Post Mortem Skill for Claude & Codex | AI Skills Catalog