◆ C#

Prepare work handover documentation

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 taskGenerate the handover document for the 'User Authentication Service' project. Include the…+
Generate the handover document for the 'User Authentication Service' project. Include the current codebase, deployment pipeline details, outstanding known bugs, and contact information for the key stakeholders, then save it to the shared drive for the incoming team.
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 finalize this handover document for the new team, make sure it clearly highlights the…+
Before I finalize this handover document for the new team, make sure it clearly highlights the critical dependencies for the 'Order Management System' module and flags any areas where our current documentation is incomplete or outdated, so they don't get stuck on day one.
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 lead developer for the 'Reporting Engine' project just gave notice, and their last day is…+
The lead developer for the 'Reporting Engine' project just gave notice, and their last day is Friday.
The lead developer for the 'Reporting Engine' project just gave notice, and their last day is Friday. I'm afraid we'll miss critical details in their handover, especially regarding the custom data transformations. The new hire starts next Monday, and I can't tell if the existing wiki covers enough. What are the most crucial pieces of information to capture in this short time, and what's the best way to extract them without overwhelming them in their last days?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself spending too much time explaining basic system architecture to new hires…+
I often find myself spending too much time explaining basic system architecture to new hires after a handover.
I often find myself spending too much time explaining basic system architecture to new hires after a handover, which wastes everyone's time. It feels like our handover documents miss the 'why' behind certain design choices. What habit should I change to ensure our handover documentation consistently provides enough context for a new developer to quickly become self-sufficient?
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 C#'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.