new-hire-onboarding-plan

$npx mdskill add Significant-Gravitas/skills-catalog/new-hire-onboarding-plan

Use this once a start date and manager are confirmed.

SKILL.md

.github/skills/new-hire-onboarding-planView on GitHub ↗
---
name: "new-hire-onboarding-plan"
description: "Build a 30-60-90 onboarding plan with first-week schedule, milestones, owners, and check-ins."
triggers: ["onboarding plan", "new hire", "first week", "30-60-90", "employee onboarding"]
version: "1"
---

# New hire onboarding plan

Use this once a start date and manager are confirmed.

## Start from the role's goals

Ask for the role description, what the person must own by day 90, the
manager, a buddy, the teams they will work with, and the tools they need.
Turn the day-90 goal into a 30-day and 60-day step. If the goal is vague, ask
the manager for one outcome that would show the hire is settled.

## Build the plan

- Before day one: contract steps HR owns, equipment, accounts, and a welcome
  note for the manager to send.
- Week one: access, people to meet, where decisions are written down, and one
  small first task with the buddy.
- Days 30, 60, and 90: one or two outcomes each, with how they will be seen.

Give every item an owner and a date. Keep week one about access and people,
not output.

## Check-in points

Set check-ins at the end of week one, day 30, day 60, and day 90, with three
questions for each: what is going well, what is blocking, and what help is
needed.

Never add personal details the manager did not share. Do not send the plan,
book meetings, or create accounts yourself; the manager approves and runs it.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.