Use casesFollow-ups

Round up unresolved Figma comments before they go stale

Mitra collects the unresolved comments scattered across your Figma files. Every Friday afternoon the agent posts them to Slack as one checklist, grouped by file and by owner, with anything older than a week flagged. Each run is recorded step by step.

Runs: Fridays at 3pm
Used by: Design

The prompt

Every Friday at 3pm, post the unresolved comments in our Figma files to #design, grouped by owner. Flag anything older than a week.

Figma

Slack

Linear

Build this agent

200 credits to start · no credit card

What the agent actually does.

Walk the Figma files
The agent opens each file you named and collects every comment still unresolved, with who left it and when.
Group by file and owner
Comments sit under the file they live in, then under the person expected to answer them.
Flag what has gone stale
Anything older than a week is marked, because a comment from three weeks ago is a different problem.
Post the checklist
One Slack post, one checkbox per comment, each linking straight back to the thread in Figma.
Open issues for real work
Comments that mean a change rather than a reply become Linear issues, so they enter the queue.

Make it yours.

For the design lead whose Figma files carry weeks of comments nobody answered, with no list of them anywhere. Change any of this by saying so — there is nothing to rewire.

Move the run to Monday, so the week opens with the list.
Send each person their own comments instead of one shared checklist.
Skip the Linear issues and keep it as a Slack checklist only.

Questions, answered.

How do I find unresolved comments across all my Figma files?

Mitra reads every file you point the agent at and pulls the comments still marked unresolved, then posts them as one checklist in Slack. Figma has no view that spans files, so the agent does that walk for you each Friday. Comments older than a week get flagged.

Can an agent turn design feedback into tickets?

Yes. Mitra opens a Linear issue for any comment that means real work, and leaves the quick ones on the Slack checklist. You decide where that line sits when you describe the job, and every issue the agent files is recorded, so nothing appears without a trace.