aar

Automate post-action analysis by correlating data from HISTORY.md and COP.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dabrewskie/owens-lifeos --skill aar-dabrewskie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aar
Source: https://github.com/dabrewskie/owens-lifeos/tree/main/skills/_archive/aar
Command: npx skills add https://github.com/dabrewskie/owens-lifeos --skill aar-dabrewskie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured post-action analysis to identify lessons learned and feed improvements back into Life OS, reducing repeating mistakes and strengthening decision-making.

Core Features & Use Cases

  • Automated AAR workflow: orchestrates data gathering from HISTORY.md, COP.md, morning-sweep-latest.md, and eod-close-latest.md to compare planned vs actual performance.
  • Pattern identification and logging: detects recurring issues and records actionable insights into HISTORY.md, COP.md, and related domain logs.
  • System improvement enablement: suggests changes to tasks, SKILLs, and domain execution flows for future cycles.

Quick Start

Trigger an AAR for the current period to generate lessons learned and system improvement recommendations.

Frequently Asked Questions about aar

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

FAQPage Schema
How do I automate post-action analysis to identify lessons learned?▼

Automate post-action analysis by orchestrating data gathering from HISTORY.md, COP.md, and morning sweep archives to compare planned versus actual performance. This structured workflow identifies recurring issues and logs actionable insights back into your system.

What is the best way to detect repeating mistakes in my weekly cycle reviews?▼

Detect repeating mistakes by comparing planned tasks against actual outcomes using multi-source data correlation. The analysis pulls from EOD closes and history logs to identify recurring patterns and suggests improvements for future execution cycles.

How does pattern detection work when logging actionable insights to HISTORY.md?▼

Pattern detection works by correlating data across your morning sweeps, EOD closes, and existing history logs. It identifies recurring issues from these sources and automatically records the extracted lessons directly into HISTORY.md and related domain logs.

Can I synchronize lessons learned across different domains using COP.md?▼

Yes, you can synchronize cross-domain changes by feeding identified lessons directly into COP.md. The analysis compares plans against outcomes and updates the common operating picture to ensure continuous system improvement across all domains.

Do I need morning sweep archives to run an event-driven AAR?▼

You need morning sweep archives and EOD close data to run a comprehensive event-driven AAR. The analysis uses these sources alongside HISTORY.md and COP.md to accurately compare your initial plans against the final actual outcomes.

Why does my structured post-action analysis suggest changes to domain execution flows?▼

Structured post-action analysis suggests changes to domain execution flows to enable system improvement and prevent recurring issues. By comparing planned versus actual performance, it identifies actionable modifications for future tasks and domain skills.