aar

Included with Lifetime

$97 forever

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.

Code Review

What this skill does


# 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

Files: 4

Size: 15.4 KB

Complexity: 36/100

Category: Code Review

Source: https://github.com/neurofoo/agent-skills/tree/main/aar

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts