◆ Asana

Archive tasks locally

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 completed tasks from the 'Product Launch v2.0' project that were finished before…+
Archive all completed tasks from the 'Product Launch v2.0' project that were finished before January 1st, 2024, to my local drive. I need to clear out the active project view.
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 'Holiday Marketing Campaign 2023' project tasks, make sure I've captured…+
Before I archive the 'Holiday Marketing Campaign 2023' project tasks, make sure I've captured any final comments or lessons learned. I want to be able to easily reference why certain decisions were made next year. Don't just hide them; make sure the key takeaways are preserved.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy active project list for 'Client Deliverables' is getting unmanageably long, making it hard…+
My project list is getting unmanageably long, but I'm hesitant to archive tasks because I might need to reference them later.
My active project list for 'Client Deliverables' is getting unmanageably long, making it hard to find current work. I want to archive older, completed tasks, but I'm afraid I'll lose access to important historical context or client feedback if I just move them out of sight. I can't risk not having that information if a question comes up. What's the best way to archive these tasks without losing the ability to quickly retrieve specific details later?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy projects often become cluttered with hundreds of completed tasks, making it difficult to…+
I keep projects cluttered with old tasks because I'm afraid of losing historical context.
My projects often become cluttered with hundreds of completed tasks, making it difficult to focus on current work. I hesitate to archive them because I worry about losing valuable historical context or the ability to quickly look up past decisions and discussions. This fear keeps my active projects messy. What habit can I change to keep my projects clean while still preserving important historical information?
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.