What it does
Pulls metrics, comments, and tasks from ClickUp (or similar), then drafts a retrospective summary with highlights, lessons, and action items.
Why I recommend it
Teams rarely document learnings. Automating retros ensures institutional knowledge isn’t lost and improvements actually get assigned.
Expected benefits
- Faster post-mortems after sprints/projects
- Actionable insights with owners
- Searchable knowledge base for future teams
- Consistent format execs can skim quickly
How it works
Project status set to complete -> automation collects task statuses, time tracking, blockers, comments -> Claude structures retro sections (What went well, What didn’t, Metrics, Experiments, Next steps) -> publishes to Notion/Confluence and notifies team for edits.
Quick start
Export a recent project board to CSV and feed highlights into Claude manually to evaluate summary quality.
Level-up version
Benchmark metrics vs previous projects, auto-create follow-up tasks, and map learnings to a global database with tags (team, tech, client).
Tools you can use
PM: ClickUp, Jira, Asana
Docs: Notion, Confluence
Automation: Zapier, Make, Workato
AI: Claude, ChatGPT
Also works with
Agile sprint retros, marketing campaign wrap-ups, event recaps.
Technical implementation solution
- No-code: ClickUp webhook -> Zapier -> Claude -> Notion page + Slack link for comments.
- API-based: Data warehouse aggregates metrics -> Claude API -> Confluence API page creation -> Jira tickets auto-created for action items.
Where it gets tricky
Capturing qualitative nuance, ensuring accountability for next steps, and avoiding sensitive commentary being shared too widely.
