Build an onboarding plan for a new hire

Needs the process document first. Run Document onboarding process once before this. This prompt invents nothing — if your process doc doesn't say who owns a task, it flags the gap instead of guessing.

How it works

1. Finds your process document in a connected folder (canonically processes/onboarding.md) — by content, not just name. If it can't find it, it stops and tells you, rather than building a plan from generic knowledge.
2. Works out which hire details matter — role, department, start date, country — based on where your process actually branches, and asks only for what's missing.
3. Reads the department document for this role (meeting list, 30/60/90 outline, documents to copy).
4. Builds the review pack: every task with exactly one owner and a real due date; the welcome email; the first-week schedule; the draft 30/60/90 (marked DRAFT — the manager owns it); the copy list. Tasks with no clear owner go into a separate "needs an owner" list for you.
5. Shows you everything and waits. Nothing is created anywhere until you explicitly say go.
6. Pushes on approval — tasks into whatever tool your process document names (Slack lists, Wrike, Monday, Asana…), calendar invites checked against everyone's availability and the country's public holidays, and per-hire document copies. Gaps stay gaps; nothing gets pushed with a guessed owner.

What you need to give it

• The hire's basic details (it only asks for the ones your process branches on).
• A connected folder containing your process document and the department document — or paste them in.
• An explicit "go" before anything is created in your tools.

What you get back

• A review pack: hire details, task list, "needs an owner" list, welcome email, first-week schedule, 30/60/90 draft, documents to duplicate — plus a list of gaps to close before pushing.
• After approval: tasks, calendar invites, and document copies created in your tools, with a short report of what was made, where, and what couldn't be (and why).

How to run it

Copy the whole file from onboarding-plan.md, fill in what you know about the hire in the first line (role, department, manager, start date, country), and paste it into a new AI conversation.

Good to know

The new hire isn't invited to meetings before their account exists, first days aren't placed on public holidays, and re-running the prompt updates rather than duplicates. Nothing is sent to the new hire or the manager unless you ask for it — creating the plan and announcing it are two different decisions.