skills.rest
ResearchMonkey
ResearchMonkeyCOMMUNITY
Explore all skills by this author →
GitHub

aar

Audit tests, docs, and memory to identify gaps and output structured recommendations.

Updated Apr 6, 2026
Search Tags:#audit#retrospective#post-mortem#engineering#process-improvement#lessons-learned#aar
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill aar-researchmonkey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aar
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.claude/skills/aar
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill aar-researchmonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After Action Review helps teams surface gaps, missed requirements, and overlooked learnings from recent work to prevent recurrence.

Core Features & Use Cases

  • Identify gaps such as dropped tests, missing documentation, stale memory, and process deviations across sessions, hotfixes, batches, or epics.
  • Capture actionable lessons and assign follow-up owners to close gaps in future work.
  • Use case: After finishing a sprint or deployment, run aar to generate a concise post-mortem and improvement plan.

Quick Start

Run the aar skill on your latest session artifacts to generate an actionable post-mortem report.

Frequently Asked Questions about aar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a post-mortem review for a software hotfix or sprint?▼

A post-mortem review audits recent work by validating tests, docs, and memory against quality gates to identify gaps. It outputs structured recommendations and assigns follow-up owners to prevent recurrence in future deliveries.

What is an after action review in software engineering?▼

An after action review surfaces gaps, missed requirements, and overlooked learnings from recent engineering work. It reads a canonical protocol to audit sessions, hotfixes, batches, or epics, generating an actionable improvement plan.

Can I run a retrospective on batch deployments and epics?▼

Yes, retrospectives apply to sessions, hotfixes, batches, and epics across software projects. The review process validates session artifacts against quality gates to capture lessons and generate structured action items.

How do I identify dropped tests and missing documentation after a deployment?▼

Identify dropped tests and missing documentation by running an audit on your latest session artifacts. The process validates tests, docs, and memory against quality gates to surface gaps and output structured recommendations for action.

What is the best way to capture lessons learned from recent engineering work?▼

The best way to capture lessons learned is through an after action review that audits recent work artifacts. It validates against a canonical protocol, identifies process deviations, and assigns follow-up owners to close gaps.

Do I need specific dependencies to generate an actionable improvement plan?▼

No specific dependencies are required to generate an actionable improvement plan. The review process reads the canonical aar protocol and validates your session artifacts directly against quality gates to output structured recommendations.

Related Skills

Explore More Software Engineering Skills→
cenconq25cenconq25
39

sprint-plan

Generate sprint backlog files from epics and stories with ownership and velocity considerations.

Community
Intermediate
ruskibeatsruskibeats

sprint-review-execution

Verify grill-me session outcomes and create follow-up tasks for identified gaps.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

checkin

Verify build status, tests, code quality, and workflow compliance before committing.

Community
Intermediate
luyzkkluyzkk

compound-engineering

Install compound-engineering templates and run integrity checks on notes.

Community
Advanced