Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
SkillScore95Maintained
Automatic
◆Project Management pack
Last verified 8/19/2026
What it changes
Passed 21 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill95%
Checks it passed that the model alone missed
The action items table includes columns for Due and Status.
The output contains the metadata header fields Facilitator and Participants.
The document header contains metadata fields for Facilitator and Participants.
and 8 more in the full report
7 fixed14 passed either way1 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+83%
Agent turns
0%
Response time
-24%
Model gemini-3.6-flashMeasured 8/19/2026v221 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
What is the standard markdown output file naming format when saving an after-action retrospective completed on 2024-03-15 for the 'auth-service-outage' event?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies the filename format as `aar-2024-03-15-auth-service-outage.md`.
Missed
Passed
case-14 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md280 lines2 files
After-Action Report
Run a structured retrospective on a launch, incident, or completed project. Produce actionable lessons, not just a document.
This skill is for after-the-fact analysis. For active incident response, use incident-response. For planning launches, use launch-runbook.
When to use
After any incident (any severity)
After every major launch
At the end of a project (sprint retro, quarterly retro, project closeout)
When a recurring issue has happened enough times to demand investigation
When a decision didn't work out and the team wants to learn
When NOT to use
During an active incident (use incident-response)
For pre-launch planning (use launch-runbook)
For one-off bug fixes that don't merit broad analysis
Required inputs
The event being analyzed (incident, launch, project)
A timeline reconstructed from logs, chat, tickets
Participant accounts of what they observed and did
Outcomes and impact (what actually happened to users, the business)
The framework: blameless analysis
The most important principle: blameless. Without it, retrospectives produce hidden information and theatrical lessons rather than real ones.
Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, write a creative direction document, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video di