mcpbeat

Aar

neurofoo/aar

After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.

4k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
1
copies elsewhere
how many repositories repackaged it
106
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/neurofoo/agent-skills --skill aar

What comes with it

13 337 bytes besides the instruction
commands/aar.md
commands/review.md
references/examples.md

The instruction itself

8 sections, as written by the author

After-Action Review

Conduct a structured debrief to extract learning from any significant event or experience.

Instructions

Work through the four core questions honestly and specifically. Focus on events and systems, not blaming individuals.

Output Format

Event: What are we reviewing?

Date: When did it happen?

Participants: Who was involved?


1. What Was Expected?

*Before the event, what did we think would happen?*

Goals/Objectives

  • [What were we trying to achieve?]

Plan

  • [What was the plan to achieve it?]

Success Criteria

  • [How would we know if we succeeded?]

Assumptions

  • [What did we assume would be true?]

2. What Actually Happened?

*Facts only—what occurred, not why*

Timeline

| Time | Event |

|------|-------|

| [When] | [What happened] |

Outcomes

  • [What results did we get?]

Compared to Expected

| Expected | Actual | Gap |

|----------|--------|-----|

| [expectation] | [reality] | [+/-] |


3. Why the Difference?

*Analysis of the gap between expected and actual*

What Went Well (sustain these)

| Success | Contributing Factors |

|---------|---------------------|

| [what worked] | [why it worked] |

What Didn't Go Well (improve these)

| Problem | Root Cause |

|---------|-----------|

| [what failed] | [why it failed] |

Surprises

  • [Things we didn't anticipate]

4. What Do We Do Next?

*Specific actions to sustain or improve*

Sustain (keep doing these)

| Action | Owner | How to Protect It |

|--------|-------|-------------------|

| [what to continue] | [who] | [mechanism] |

Improve (change these)

| Action | Owner | By When |

|--------|-------|---------|

| [what to change] | [who] | [deadline] |


Key Takeaways

Top 3 lessons from this review:

  • [Lesson]
  • [Lesson]
  • [Lesson]

Follow-up

When will we check if improvements are working?

Guidelines

  • Do this soon—memory fades fast
  • Be specific: "Communication failed" → "We didn't update Slack until hour 3"
  • Balance: Include what went well, not just problems
  • Assign owners: Insights without ownership become forgotten
  • Make it safe: Blame shuts down honesty

$ARGUMENTS

Repackaged in 1 other repositories

same content, different owner
christophacham/agent-skills-library open on GitHub →

How to use it

Copy the folder

Take neurofoo/aar from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.