◆ Asana

Archive tasks

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskArchive all tasks related to the 'Project Phoenix' launch that were completed before September…+
Archive all tasks related to the 'Project Phoenix' launch that were completed before September 30th.
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 I archive the 'Project Phoenix' tasks, make sure we've captured all key learnings and…+
Before I archive the 'Project Phoenix' tasks, make sure we've captured all key learnings and final deliverables. Double-check that all client approvals are stored and that the post-mortem notes are linked, so we don't lose any valuable information for future projects.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm about to archive all 'Project Phoenix' tasks, but I'm unsure if every final client sign-off…+
I'm about to archive 'Project Phoenix' tasks, but I'm unsure if all final client sign-offs are in the system.
I'm about to archive all 'Project Phoenix' tasks, but I'm unsure if every final client sign-off has been properly uploaded and linked. Our procurement lead, Emily, is very particular about documentation. I'm afraid if I archive prematurely, we'll have issues later if she requests proof. What's the best next step to confirm everything is complete before archiving?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternArchiving tasks always feels like a rushed afterthought, often leading to incomplete records…+
Archiving tasks always feels like a rushed afterthought, leading to incomplete records.
Archiving tasks always feels like a rushed afterthought, often leading to incomplete records and missing information when we need to reference past projects. This costs us time and credibility with clients. What habit should I change to ensure archiving is a thorough and consistent part of our project lifecycle, so we always have complete historical data?
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 Asana'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.