Aar Loop — AI skill for Claude Code
Run an After Action Review after any AI session and write concrete lessons so your agent stops repeating mistakes.
How to install Aar Loop
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open coopersimson96/aar-loop and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Aar Loop does
Run an After Action Review after any AI session and write concrete lessons so your agent stops repeating mistakes. A manual Reflexion loop, built on the US Army's AAR method.
Alternatives in AI
- Bmad Method — Breakthrough Method for Agile Ai Driven Development 42712 382 2 42.9k ★
- Model Update — 增量更新财务模型 — 用新财报/新指引/修正假设重算 DCF 内在价值、Comps 隐含价、投资逻辑与目标价,输出 before→after delta 6.6k ★
- Cwc Long Running Agents — Claude Code's built-in /goal command gives you a generator/evaluator loop out of the box: set a completion con 668 ★
README
AAR Loop
A human-run version of Reflexion for AI agents, built on a military method that's been standard practice for fifty years.
Run `/aar-loop` after any task or session. It does three things:
- Reviews the session with the US Army's 4-question After Action Review.
- Finds what's worth fixing and writes the improvement straight into your skills or rules files, so the fix is there before you need it again, not just written down somewhere.
- Saves the lessons to a persistent LESSONS.md file that your AI loads next time.
Point the next session at that file (and at whatever skill or rule got patched) and the agent stops repeating the same mistake. Run it every session and the agent compounds instead of restarting from zero each time.
Where the method comes from
The US Army formalized the After Action Review in the mid-1970s, in the years after Vietnam, as a structured debrief for training exercises. It became official doctrine in 1993 with field manual TC 25-20, and it's still run after every rotation at the National Training Center, Fort Irwin, one of the most realistic combat training environments in the world. Fifty years of continuous use on one method, because the mechanism is simple and hard to argue with: separate the debrief from blame, ask what was supposed to happen versus what actually happened, and the gap tells you exactly what to fix before the next fight.
The 4 questions, verbatim:
- What was supposed to happen?
- What actually happened?
- Why was there a difference?
- What do we do the same or differently next time?
The research parallel
This is also, functionally, a manual version of **Reflexion** (Shinn et al., 2023, [arXiv:2303.11366](https://arxiv.org/abs/2303.11366)): an agent framework where a model generates a verbal self-reflection after a failed attempt, stores it in an episodic memory buffer, and carries it into the next attempt. Reflexion agents that keep their reflections outperform agents that start ev
Related Skills
Socratic Learning
Socratic Method: Reverse Questioning — Agent Skill. AI asks you questions in return, guiding you to clarify yo
Quality Babysit
AI Quality Ratchet babysitting loop — read quality-report.md, fix one regression at a time, push, repeat. PR-1
Opus Magnum
The Great Work for Claude Code — an adaptive method for long-horizon, high-trust AI builds. Triage, elements,
Open Sheet
The spreadsheet framework built for agents — write the model as React, export a live .xlsx. The third medium,
Recovery Classification
Enforces Law 4 (Verify Before Reporting) of the 7 Laws of AI Agent Discipline. After any failure in the verifi
ML Impl
Full implementation loop - plan, write, and review code (Meta-Loop Steps 3.1-3.4)
Related Agents
Landing Builder
Use for the structural spine of the Chain Method build (landing-page core) — from the subject/audience/job sta
Part 13: Memory Bridge (Give Coding Agents Your Brain)
When you spawn Codex or Claude Code to build something, they start blind. They don't know your architecture de
Community Publisher
Publishes one already validated community demo through a contributor fork and pull request, then stops for mai