Use casesStatus updates

A weekly design digest nobody has to open Figma to read

Mitra posts a weekly summary of what design actually shipped, what is waiting on review and what is blocked. The agent reads the files themselves rather than a status field somebody remembered to update. The digest goes to Notion and a short version to Slack.

Runs: Fridays at 5pm
Used by: Design

The prompt

Every Friday at 5pm, write a design digest from what moved in Figma: shipped, in review, and blocked on whom. Save it to Notion and post the headlines to #design.

Figma

Notion

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Read what actually moved
The agent looks at pages added, frames marked done and review requests opened, rather than a status column.
Sort into three buckets
Work is grouped as shipped, in review, or blocked, because those are the only states anyone outside design needs.
Name what is blocked
A blocked item is useless without the reason, so each one carries who or what it is waiting on.
File it and post it
The full digest goes to Notion for the record, and the headlines to Slack for people who will not click through.

Make it yours.

For design leads who spend Friday afternoon writing the same update, and everyone outside design who keeps asking for it. Change any of this by saying so — there is nothing to rewire.

Send it as an email to stakeholders instead of a Slack post.
Run it fortnightly to match a two-week design cycle.
Split it per squad, so each team gets only its own work.

Questions, answered.

How can I share design progress without writing a weekly update?

Mitra reads your Figma files on a schedule and writes the update for you, sorting work into shipped, in review and blocked. The digest lands in Notion and a short version goes to Slack. You describe once what you want in it, in plain English.

Will the digest be accurate if we forget to update statuses?

Mostly, because Mitra reads what changed in the files rather than trusting a status field. The agent can only report what is visible in Figma, so work done somewhere else stays invisible. That is usually a sign the work belongs in Figma.