界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
开发与工程 · SKILL.md

aar

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.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: aar description: 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. user-invocable: true

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

我的收藏