メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
Cynefin sense-making framework categorizing problems as Simple, Complicated, Complex, Chaotic, or Confused to select the right approach. Use when unsure how to tackle a problem.
Design Thinking process—Empathize, Define, Ideate, Prototype, Test. Use for product design, solving ambiguous problems, or when you don't know what users really need.
| 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 |
Conduct a structured debrief to extract learning from any significant event or experience.
Work through the four core questions honestly and specifically. Focus on events and systems, not blaming individuals.
Event: What are we reviewing? Date: When did it happen? Participants: Who was involved?
Before the event, what did we think would happen?
Goals/Objectives
Plan
Success Criteria
Assumptions
Facts only—what occurred, not why
Timeline
| Time | Event |
|---|---|
| [When] | [What happened] |
Outcomes
Compared to Expected
| Expected | Actual | Gap |
|---|---|---|
| [expectation] | [reality] | [+/-] |
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
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:
Follow-up When will we check if improvements are working?
$ARGUMENTS
