◆ JavaScript

Edit work items in bulk

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 taskUpdate the status of all open bugs assigned to me in the 'Login Flow' project to 'In Progress'…+
Update the status of all open bugs assigned to me in the 'Login Flow' project to 'In Progress' and set their priority to 'High'.
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 update these 20 user stories to 'Done', make sure they all have a 'Verified' tag and…+
Before I update these 20 user stories to 'Done', make sure they all have a 'Verified' tag and that the 'Estimated Effort' field is cleared, so we don't accidentally carry over old estimates.
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 just pushed a big change to the 'Checkout' module, and now the product owner is asking why…+
I just got a Slack from the product owner asking why the 'Checkout' feature isn't showing up in the latest staging build.
I just pushed a big change to the 'Checkout' module, and now the product owner is asking why it's not live on staging. I'm afraid I might have inadvertently reverted a critical flag or missed a deployment step for this specific feature. I can't tell them I'm not sure if my changes broke something. What's the fastest way to check if my recent changes impacted the feature flag settings for 'Checkout' across all environments, and what's the best next step if they did?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly losing time manually updating multiple related tickets—bugs, tasks, and…+
I keep finding myself manually updating related tickets after a major feature is released.
I'm constantly losing time manually updating multiple related tickets—bugs, tasks, and stories—after a major feature like 'User Profiles' goes live. This often leads to inconsistencies and missed updates. What habit can I change to ensure all linked work items are automatically or systematically updated to 'Done' or 'Closed' when the primary feature is deployed, without me having to chase them down one by one?
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 JavaScript'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.