◆ Microsoft Azure

Track work in Azure Boards

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 work item for 'Bug: Login button not responding on mobile'. Assign it to David and…+
Create a new work item for 'Bug: Login button not responding on mobile'. Assign it to David and set the priority to High. This needs to be tracked immediately.
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 daily stand-up, review all open bugs for the 'PaymentGateway' project. Prioritize…+
Before the daily stand-up, review all open bugs for the 'PaymentGateway' project. Prioritize them based on customer impact and technical complexity, and flag any that are blocking critical path items for the upcoming sprint. I need to present a clear picture to the team.
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 client just reported a critical production bug, but I can't find an existing work item that…+
The client just reported a critical bug, but I can't find an existing work item that accurately describes it.
The client just reported a critical production bug, but I can't find an existing work item that accurately describes it, and I'm unsure if it's a new bug, a regression, or a misreported existing issue. I'm afraid of creating duplicates or miscategorizing it, which could delay resolution. What's the best way to quickly search for similar issues or create a new, properly linked work item to ensure it gets immediate attention without causing confusion?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle to keep track of all my tasks, their dependencies, and their current…+
I consistently struggle to keep track of all my tasks and their dependencies across multiple projects in Azure Boards.
I consistently struggle to keep track of all my tasks, their dependencies, and their current status across multiple projects. This leads to missed deadlines and a feeling of being overwhelmed. What habit can I change to better organize my work items, visualize my workload, and ensure I'm always aware of what needs my immediate attention?
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 Microsoft Azure'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.