retro

Automated weekly team retrospectives combine git commits, session logs, changelogs, and validation records into a structured markdown report. The aggregated document provides per-agent performance breakdowns, shipping streaks, and blocker analysis for weekly planning.

A team-aware retrospective ingests docs/agent-notes and communication history to evaluate per-agent tasks, bugs found, and idle or blocked statuses. It processes this data to generate actionable recommendations and identify carry-over items for leadership.

Per-agent performance metrics can be generated by aggregating changelogs, validation logs, and Slack exports. The process calculates individual tasks completed, blockers, and test pass rates, flagging any idle or blocked agents for review.

This retrospective approach works with Jira exports and validation logs by consuming them alongside git commit history and session logs. It outputs a full markdown report to docs/retros and posts a short summary to Slack.

Tracking shipping streaks and test health metrics is done by summarizing features shipped, commit counts, LOC changes, and test additions from recent git commits. The resulting analytics highlight pass rates and identify PD decision load bottlenecks.