post-mortem

Run a council retrospective and generate a structured post-mortem report.

418|40|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/boshu2/agentops --skill post-mortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/boshu2/agentops/tree/main/skills/post-mortem
Command: npx skills add https://github.com/boshu2/agentops --skill post-mortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires council, retro, beads, and includes references (resource) components.

What problem does it solve?

This Skill helps teams finalize and validate completed work by orchestrating a council review and extracting actionable learnings, ensuring alignment with plans and documented outcomes.

Core Features & Use Cases

  • Council validation: Run a deep, retrospective council to confirm that the delivered work matches the planned objectives.
  • Learnings extraction: Use /retro to surface patterns, improvements, and reusable knowledge from the completed epic.
  • Post-mortem reporting: Generate and store a structured post-mortem document at .agents/council/YYYY-MM-DD-post-mortem-<topic>.md.
  • Advanced workflows: Support cross-vendor reviews or extended exploration with flags like --mixed, --explorers, or --debate to handle high-stakes ships.

Quick Start

Use the post-mortem skill to wrap up recent work:

  • /post-mortem
  • /post-mortem epic-123
  • /post-mortem --deep epic-123
  • /post-mortem --debate epic-123

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I generate a post-mortem report for a completed epic?

To generate a post-mortem report, you run a deep retrospective council validation on the epic, extract learnings via retro, and write the structured outcomes to a dated markdown file in the .agents/council directory.

What is the best way to extract actionable learnings from a retrospective?

The best way to extract learnings from a retrospective is to use a dedicated retro command on the completed epic, surfacing patterns and improvements for validation by a council before generating the final report.

Does the council validation process support high-stakes project reviews?

Yes, council validation supports high-stakes reviews by applying extended flags like --mixed, --explorers, or --debate to handle cross-vendor reviews and extended exploration during the retrospective.

Can I run a post-mortem on recent epics automatically?

Yes, you can run a post-mortem on recent epics by invoking the skill without a specific epic identifier, automatically targeting recent work for plan load, council validation, and learnings extraction.

Where are post-mortem reports stored?

Post-mortem reports are stored as structured markdown files at .agents/council/YYYY-MM-DD-post-mortem-<topic>.md, ensuring chronological tracking of council validations and learnings.

How do I validate completed epic deliverables against planned objectives?

You validate completed epic deliverables against planned objectives by running a deep council validation with a retrospective preset, confirming alignment before extracting learnings and writing the post-mortem.