after-action-report

Run structured after-action reviews using a six-section framework.

523|69|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/rampstackco/claude-skills --skill after-action-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: after-action-report
Source: https://github.com/rampstackco/claude-skills/tree/main/skills/after-action-report
Command: npx skills add https://github.com/rampstackco/claude-skills --skill after-action-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run structured after-action reviews on launches, incidents, or completed projects. This skill helps teams capture timelines, root causes, contributing factors, and actionable lessons to improve future work and reduce repeat issues.

Core Features & Use Cases

  • Six-section framework: Summarizes the event, reconstructs the timeline, analyzes root causes, identifies contributing factors, highlights successes, and defines concrete action items.
  • Facilitated, blameless process: Encourages candid reflection and system-wide improvements without blaming individuals.
  • Templates and guidance: Provides a ready-to-use structure for documenting findings and tracking follow-up.

Quick Start

Schedule the AAR, gather inputs (timeline, logs, and participant notes), run the facilitator-led six-section meeting, and publish the final AAR with tracked action items.

Frequently Asked Questions about after-action-report

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

FAQPage Schema
How do I run a blameless postmortem after a project launch or incident?

To run a blameless postmortem, gather timeline data, logs, and participant notes, then facilitate a structured review using a six-section framework covering summary, timeline, root cause analysis, contributing factors, successes, and action items to produce a publishable document.

What is a blameless retrospective and how does it prevent repeat incidents?

A blameless retrospective is a structured review process that analyzes incidents or completed projects to drive system-wide improvements without blaming individuals, capturing lessons learned to reduce repeat issues and improve future work.

What do I need to prepare for an after-action review session?

To prepare for an after-action review, you need to schedule the meeting and gather inputs including the event timeline, relevant logs, and participant notes to facilitate the six-section analysis and generate tracked action items.

Can I use this structured retrospective framework for completed projects, not just incidents?

Yes, you can use this retrospective framework for completed projects, launches, or incidents. It captures timelines, root causes, and contributing factors, highlights successes, and defines concrete action items applicable to any post-event lessons-learned session.

How do I document root cause analysis and contributing factors for a lessons-learned session?

Document root cause analysis and contributing factors by following the facilitated six-section framework, which reconstructs the event timeline from participant notes and logs to identify system-wide issues and generate tracked action items.

What is the best way to track action items generated from a postmortem?

The best way to track action items from a postmortem is to use the outputted publishable after-action review document, which defines concrete action items alongside root causes and contributing factors to ensure accountability for future improvements.