$ ls -la drwxr-xr-x docs/ $ run script
◆ Bash

Manage employee offboarding processes

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 Bash tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFor the employee offboarding, I need to revoke access for Jane Doe from all systems, delete her…+
For the employee offboarding, I need to revoke access for Jane Doe from all systems, delete her home directory, transfer ownership of her active projects to John Smith, and archive her email account. Do this by end of day Friday.
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 run the offboarding script for Jane Doe, make sure it handles open network connections…+
Before I run the offboarding script for Jane Doe, make sure it handles open network connections gracefully, logs every step with timestamps, and verifies file permissions before deletion, so we don't accidentally lock ourselves out or lose data.
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 offboarding script for Sarah Connor just hung after revoking her VPN access, and I can't…+
The offboarding script for a departing employee just failed mid-execution.
The offboarding script for Sarah Connor just hung after revoking her VPN access, and I can't tell if her home directory was deleted or not. Her manager is breathing down my neck because she had access to sensitive client data. I'm worried about data leakage if she still has access, but also data loss if I rerun it blindly. What's the best way to diagnose where it stopped and safely resume, or roll back, without causing more problems?
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 losing sleep because offboarding scripts randomly fail on edge cases like non-existent…+
I keep getting called at 2 AM because offboarding scripts fail on edge cases.
I keep losing sleep because offboarding scripts randomly fail on edge cases like non-existent directories or locked files, forcing me to manually intervene and risking compliance breaches. What habit should I change to ensure these scripts are robust and self-healing, so I don't have to babysit every offboarding?
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 Bash'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.