aar

Conduct structured after-action reviews using git evidence and session artifacts.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/basher83/domain-chassis --skill aar-basher83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aar
Source: https://github.com/basher83/domain-chassis/tree/main/skills/aar
Command: npx skills add https://github.com/basher83/domain-chassis --skill aar-basher83

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured framework for conducting after-action reviews, helping to identify what went well, what didn't, and what can be improved in future work sessions.

Core Features & Use Cases

  • Structured Retrospective: Guides users through a systematic review of a completed session.
  • Data Gathering: Spawns subagents to collect evidence from git, artifacts, and session logs.
  • Analysis & Synthesis: Helps categorize friction points and distill actionable lessons learned.
  • Use Case: After a complex development sprint, use this Skill to analyze the process, identify bottlenecks in the CI/CD pipeline, and document improvements for the next sprint.

Quick Start

Use the aar skill to perform an after-action review of the last development session.

Frequently Asked Questions about aar

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

FAQPage Schema
How do I conduct an after-action review for a completed development sprint?

An after-action review is conducted by gathering git evidence, analyzing session artifacts, and synthesizing findings into actionable lessons learned. This Skill systematically guides you through the process to identify methodology and infrastructure issues for future refinement.

What is the best way to capture lessons learned from work sessions?

Capturing lessons learned involves analyzing session logs and categorizing friction points to distill reusable principles. This Skill automates the data gathering and synthesis to propose concrete improvements for your process.

How do I run a structured retrospective to identify CI/CD pipeline bottlenecks?

A structured retrospective analyzes completed work sessions by spawning subagents to collect evidence from git and artifacts. It identifies infrastructure or agent behavior issues and documents concrete improvements for the next sprint.

Can I perform a post-mortem analysis on any domain or is it limited to software engineering?

You can perform a post-mortem analysis across any domain because the Skill facilitates structured retrospective analysis by gathering artifacts and identifying methodology issues. It requires systematic data gathering to produce reusable principles.

Do I need any dependencies to generate an after action review from git evidence?

No dependencies are required to generate an after action review from git evidence. The Skill relies solely on its internal scripts to analyze artifacts and session logs without external dependencies.

Why should I use a structured debrief instead of manually reviewing session logs?

A structured debrief systematically categorizes friction points and proposes concrete improvements, whereas manual review often misses reusable principles. This Skill automatically distills findings into actionable principles for process refinement.