Weekly Review

Automate a metric-driven weekly retrospective with KALM findings and SMART actions.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill weekly-review-aaronjmars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Weekly Review
Source: https://github.com/aaronjmars/aeon/tree/main/skills/weekly-review
Command: npx skills add https://github.com/aaronjmars/aeon --skill weekly-review-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly reviews often turn into subjective summaries that don’t reliably track whether last week’s actions actually shipped or improved outcomes based on objective data.

Core Features & Use Cases

  • Evidence-based retrospective (KALM): Frames weekly findings as Keep/Add/Less/More, each backed by logs, commit lines, or issue IDs.
  • Closed-loop tracking: Audits last week’s “Next week priorities” to mark items as shipped, slipped, abandoned, or blocked.
  • SMART next-week execution: Converts the top prioritized findings into concrete actions with deadlines within the next 7 days and verifiable “Done when” criteria.

Quick Start

Run Weekly Review to generate a metrics-first article, audit last week’s priorities, and produce SMART checklist actions for the coming week.

Frequently Asked Questions about Weekly Review

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

FAQPage Schema
How do I automate a metric-driven weekly retrospective for GitHub repository activity?

Automate a weekly retrospective by aggregating activity logs, issue changes, and repository activity over a rolling 7-day window. The Skill enforces evidence-backed KALM findings and produces a structured article with verifiable action items.

How do I track whether last week's priorities were actually shipped or slipped?

Closed-loop tracking audits last week's priorities by marking items as shipped, slipped, abandoned, or blocked. This verifies whether actions actually shipped based on objective metrics like commit lines and issue IDs.

What is the best way to convert issue triage findings into SMART actions with deadlines?

Convert issue triage findings into SMART actions by prioritizing top KALM findings. The Skill transforms them into concrete actions with deadlines within the next 7 days and verifiable 'Done when' criteria.

Does the weekly review process require specific dependencies or environments to run?

The weekly review process requires no external dependencies but needs a specific environment. It aggregates inputs in a fixed order and runs the ./scripts/skill-runs script with fallback behavior to execute correctly.

Can I send notifications and emails automatically after generating a weekly review?

You can send notifications and emails automatically after generating a weekly review. The Skill conditionally dispatches these communications once it finishes writing the structured metrics-first article.