◆ Figma

Manage team tasks in Figma

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Figma tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAssign the 'Design Login Flow' task to Sarah, set its due date for next Wednesday, and update…+
Assign the 'Design Login Flow' task to Sarah, set its due date for next Wednesday, and update its status to 'In Progress'. Add a note reminding her to use the new authentication component library.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore our stand-up tomorrow morning, review all open tasks for the 'Mobile App Redesign'…+
Before our stand-up tomorrow morning, review all open tasks for the 'Mobile App Redesign' project. Identify any tasks that are blocked or overdue, flag them for discussion, and ensure all team members have clear next steps assigned so we can unblock progress and keep the project on track.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe development team just told me they can't start on the checkout flow because the designs…+
The development team just told me they can't start on the checkout flow because the designs aren't final, but I thought I'd already marked them 'Ready for Dev'.
The development team just told me they can't start on the checkout flow because the designs aren't final, but I thought I'd already marked them 'Ready for Dev'. I'm afraid there's a disconnect in our task statuses, and this will delay the launch. What's the best way to quickly verify the true status of all critical design tasks for the current sprint, and how do I prevent this miscommunication from happening again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself scrambling to understand who is working on what and the actual status of…+
I often find myself scrambling to understand who is working on what and the actual status of design tasks.
I often find myself scrambling to understand who is working on what and the actual status of design tasks, leading to missed handoffs and last-minute rushes. This creates friction with the engineering team. What habit should I change to maintain a clear, real-time overview of all design tasks and their progress, ensuring everyone is aligned and accountable?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Figma's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.