◆ Asana

Manage software development 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 taskCreate a new task for the 'Mobile App Development' project: 'Implement User Login Feature'.…+
Create a new task for the 'Mobile App Development' project: 'Implement User Login Feature'. Assign it to Raj with a due date of next Tuesday.
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 the sprint planning meeting, organize the 'Mobile App Development' backlog. Group all…+
Before the sprint planning meeting, organize the 'Mobile App Development' backlog. Group all bug fixes under 'Bug Squashing', new features under 'Feature Development', and ensure each task has an estimated effort in story points for the team to review.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentRaj just told me he can't start 'Implement User Login Feature' because he's blocked by a…+
Raj just told me he can't start 'Implement User Login Feature' because he's blocked by a dependency he can't identify.
Raj just told me he can't start 'Implement User Login Feature' because he's blocked by a dependency he can't identify, and I'm worried this will push back our release. I can't tell the product owner we didn't foresee this. What's the likely diagnosis for this blocker and what's the best next move to unblock Raj and keep the sprint on track?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find that developers are blocked by unidentified dependencies, leading to delays…+
I frequently find that developers are blocked by unidentified dependencies, leading to delays in our software releases.
I frequently find that developers are blocked by unidentified dependencies, leading to delays in our software releases. This always causes friction with the product team. What habit should I change in how I set up and manage development tasks to proactively identify and address dependencies before they become blockers?
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.