◆ MATLAB

Update similar tasks 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
See the prompt↓All MATLAB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskUpdate the `project_status` field to 'Completed' for all tasks in the `task_list.csv` where the…+
Update the `project_status` field to 'Completed' for all tasks in the `task_list.csv` where the `due_date` is before '2023-10-26' and the `assigned_to` field is 'Dr. Chen'.
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 send this task list to the department head, update all project tasks that are overdue…+
Before I send this task list to the department head, update all project tasks that are overdue and assigned to 'Dr. Chen' to 'Completed', but flag any that also have a 'High Priority' status. I want to make sure we don't accidentally mark a critical overdue item as done without a final check.
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 need to update the `status` column to 'Done' for about 50 tasks in the `engineering_log.xlsx`…+
I'm trying to update a batch of completed tasks, but I'm worried about accidentally changing the status of tasks that are still active.
I need to update the `status` column to 'Done' for about 50 tasks in the `engineering_log.xlsx` file that were completed last week by the 'Structures Team'. I'm afraid of accidentally marking an active project as complete, especially since some tasks have similar names. The project manager needs this by lunch. What's the safest way to identify and update only the truly finished tasks without risking data corruption, and what's the best way to verify before committing?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep making small but significant errors when I have to update multiple entries that share…+
I frequently make manual errors when updating multiple similar entries in our project logs.
I keep making small but significant errors when I have to update multiple entries that share common criteria in our project databases. It's usually a typo in a filter or an accidental overwrite. This costs us time in corrections and erodes my credibility. What habit should I change in how I approach bulk updates to ensure accuracy and prevent these recurring mistakes?
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 MATLAB'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.