Most retros rely on memory. People talk about what they remember from the last few weeks, and the patterns that actually slowed things down get missed.
Instead of relying on memory, your agent drafts project retrospectives from planned outcomes, completed tasks, comments, and activity history. It highlights delivered results, surfaces recurring blockers, identifies process friction, and proposes structural improvements for the team to discuss.
What the agent starts with
Two records of the same finished project.
- What was agreed — three call transcripts. A kickoff where legal was budgeted at "a couple of days". A mid-point check where the reward changed from credit to cash and nobody told legal, so a second review appeared. A closing call where the analytics work turns out to have gone in at the last minute.
- What happened — the finished board. Twenty tasks, five stages, including three that aren't mentioned in any transcript because they were added mid-flight.
The prompt
Copied
What comes back
At most five findings, each carrying its own evidence — the tasks, the dates, the number of days.
Written about the process rather than about people.
And the three changes land as subgoals under the retro, so they can actually be closed.
