Use casesStatus updates
A design review agenda built from what actually changed
Mitra writes the design review agenda from the work itself. The agent reads what changed in Figma since the last review and orders the files by how much moved. The list goes to Slack before the meeting, and your calendar tells the agent when the last review was.
At 9am on Wednesdays, post an agenda to #design listing the Figma files that changed since last week's review.
200 credits to start · no credit card
What the agent actually does.
Find the last review
Google Calendar gives the agent the date of the previous review, which sets the window for everything else.
Read what moved in Figma
Files edited inside that window are collected, with who edited them and how much of each changed.
Order by how much moved
The file that changed most opens the agenda, and a nudged margin sits at the bottom or drops off.
Write a line per file
Each item gets a short note, so the room does not spend ten minutes working out what it is looking at.
Post it before the meeting
The agenda lands hours ahead, which gives people time to look at the work first.
Make it yours.
For whoever runs design review and builds the agenda from memory, ten minutes before the meeting starts. Change any of this by saying so — there is nothing to rewire.
- Cap the agenda at five files, so the review stays inside its hour.
- Post it as a comment on the calendar invite instead of in a channel.
- Add the open comments on each file underneath its line.
Questions, answered.
How do I build a design review agenda without chasing everyone?
Can Mitra tell which design work deserves review time?
Other things people stop doing.
Ready to
reclaim your day?
Build my first agent200 free credits · no credit card · nothing to install