Skip to content
Back to skills

Onboarding Plan

ASecurity

Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria.

  • 1,330 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add mohitagw15856/pm-claude-skills --skill onboarding-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Onboarding Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Onboarding Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mohitagw15856-onboarding-plan/badge)](https://www.skillsdirectory.com/skills/mohitagw15856-onboarding-plan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: onboarding-plan
description: "Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria."
---

# Onboarding Plan Skill

Creates a complete, structured onboarding plan tailored to a specific role — covering the first 90 days with clear milestones and success criteria.

## Required Inputs
- **Role and level** of the new hire
- **Team and manager**
- **Key stakeholders** they will work with
- **Top 3 priorities** for their first 90 days
- **Tools and systems** they will need access to
- **Company stage** (startup / scaleup / enterprise)

## Output Structure

### Onboarding Plan: [Name] — [Role]
**Start date:** [Date] | **Manager:** [Name] | **Buddy:** [Name]

---

### Before Day 1 (Manager checklist)
- IT setup: laptop, accounts, email, Slack, key tools
- Access provisioned to key systems
- First week calendar blocked with key meetings
- Buddy assigned and briefed
- Welcome message sent with Day 1 logistics

---

### Week 1: Orient
Theme: Listen, learn, do not act yet.

| Day | Focus | Key activities |
|---|---|---|
| Day 1 | IT setup, team intro | 1:1 with manager, team lunch |
| Day 2 | Product deep dive | Demo, key docs to read |
| Day 3 | Process and tools | Shadow key workflows |
| Day 4 | Stakeholder intros | 3-4 intro 1:1s |
| Day 5 | Week 1 debrief | Check-in, questions logged |

**Week 1 milestone:** Can describe what the company does, the team role, and their top 3 priorities.

---

### Days 8-30: Learn
Learning goals:
- Deep understanding of product from customer perspective
- Know key metrics the team is measured on
- Understand current projects and status
- Map key stakeholder relationships
- Complete all compliance/HR training

**30-day milestone:** All stakeholder 1:1s complete. 2-3 early observations shared with manager.

---

### Days 31-60: Contribute
Goals:
- Own at least one project end-to-end
- Make one meaningful contribution
- Build cross-functional relationships
- Identify one process improvement

**60-day milestone:** Delivered one tangible output. Manager says "this person is contributing."

---

### Days 61-90: Lead
Goals:
- Operating independently on core responsibilities
- Has formed and shared a point of view on priorities
- Building reputation with key stakeholders

**90-day milestone:** Ready for formal review. Clear 6-month plan in place.

---

### 90-Day Review Questions
Manager: Meeting expectations? What to double down on? What to develop?
New hire: Have the clarity, tools, support needed? What surprised you? What would you change about onboarding?

## Quality Checks

- [ ] Before Day 1 manager checklist is complete (IT, access, buddy, calendar)
- [ ] Each phase (orient/learn/contribute/lead) has a clear milestone
- [ ] 90-day review questions are included for both manager and new hire
- [ ] Plan is tailored to the specific role and level (not generic)
- [ ] Key stakeholder 1:1s are listed by name or role

## Example Trigger Phrases
- "Create a 30/60/90 day plan for a new [role]"
- "Write an onboarding plan for [name] starting as [role]"
- "Build a first 90 days roadmap for our new hire"

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…