mcpField
A
aar

aar

github.com/neurofooProductivity122100 installsUpdated 40w ago
Repository

About aar

A structured After-Action Review skill for examining significant events, comparing intended and actual outcomes, and turning lessons into owned follow-up actions. It emphasizes specific evidence and learning without assigning blame.

Key features

  1. 01Four-question review structure
  2. 02Expected-versus-actual comparison
  3. 03Successes, problems, and root causes
  4. 04Action owners and follow-up

Use cases

  1. 01Debriefing a project or incident
  2. 02Identifying causes of missed goals
  3. 03Assigning owners to improvements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/neurofoo/agent-skills --skill aar

After installing, type/aarin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

commands/
aar.md
review.md
references/
examples.md

Details

From the project README

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

TimeEvent
[When][What happened]

Outcomes

  • [What results did we get?]

Compared to Expected

ExpectedActualGap
[expectation][reality][+/-]

3. Why the Difference?

Analysis of the gap between expected and actual

What Went Well (sustain these)

SuccessContributing Factors
[what worked][why it worked]

What Didn't Go Well (improve these)

ProblemRoot 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)

ActionOwnerHow to Protect It
[what to continue][who][mechanism]

Improve (change these)

ActionOwnerBy When
[what to change][who][deadline]

Key Takeaways Top 3 lessons from this review:

  1. [Lesson]
  2. [Lesson]
  3. [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

Comments

Markdown supported