🎯

aar

🎯Skill

from neurofoo/agent-skills

VibeIndex|
What it does

Systematically review and learn from events by analyzing expectations, actual outcomes, differences, and future actions.

📦

Part of

neurofoo/agent-skills(24 items)

aar

Installation

Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add neurofoo/agent-skills
Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add neurofoo/agent-skills/thinking-frameworks
Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add neurofoo/agent-skills/prioritization-skills
Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add neurofoo/agent-skills/creative-skills
Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add neurofoo/agent-skills/learning-skills

+ 3 more commands

📖 Extracted from docs: neurofoo/agent-skills
8Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

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.

Overview

# 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:

  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

More from this repository10

🏪
neurofoo-agent-skills🏪Marketplace

Thinking frameworks and decision-making skills for Claude Code

🎯
feynman🎯Skill

Breaks down complex concepts into simple explanations, identifies knowledge gaps, researches to fill them, and refines understanding through structured learning.

🎯
socratic🎯Skill

Guides systematic questioning to deeply examine beliefs, uncover assumptions, and develop clearer understanding through structured, non-confrontational exploration.

🎯
redteam🎯Skill

Performs adversarial analysis to systematically identify and expose potential weaknesses, vulnerabilities, and failure modes in plans, systems, or strategies.

🎯
eos-style🎯Skill

Evaluates writing against Strunk & White's 21 style principles, providing actionable feedback to improve clarity, tone, and writing quality.

🎯
scamper🎯Skill

Systematically explores creative problem-solving by applying seven transformative prompts to generate innovative ideas and breakthrough solutions.

🎯
moscow🎯Skill

Prioritizes items into Must, Should, Could, and Won't categories to clarify project scope and focus critical efforts.

🎯
ooda🎯Skill

Systematically analyze complex decisions by methodically breaking down problems through observation, orientation, decision-making, and execution.

🎯
wardley🎯Skill

Maps strategic technology components across evolution stages to reveal build vs buy decisions and competitive dynamics for technology strategy.

🎯
swot🎯Skill

Conducts comprehensive SWOT analysis to evaluate strategic positioning by systematically examining strengths, weaknesses, opportunities, and threats.