Onboarding Plan Skill
Create a structured 30/60/90-day onboarding plan for any new hire.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/onboarding-plan. - Describe your job in plain words. Claude Code follows the skill from there.
npx degit mohitagw15856/pm-claude-skills/skills/onboarding-plan#main ~/.claude/skills/onboarding-planFor one project only, change the path to .claude/skills/onboarding-plan.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Onboarding Plan Skill
Show the full text106 lines
| name | description |
|---|---|
| onboarding-plan | 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
Anti-Patterns
- Do not produce a generic plan that could apply to any role — the plan must reference the specific role, team, tools, and priorities provided, not use placeholder text
- Do not skip the Before Day 1 manager checklist — IT access and system provisioning failures on day 1 destroy first impressions and waste the new hire's first week
- Do not set milestones without distinguishing between the orient, learn, contribute, and lead phases — collapsing phases produces plans where new hires are expected to lead before they understand the product
- Do not omit the 90-day review questions — the review is the accountability mechanism for the entire plan, and skipping it makes the milestones meaningless
- Do not treat the plan as a task list — each phase should have a clear theme and a milestone that describes an observable capability, not just a set of completed activities
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"
| 1 | |
| 2 | name onboarding-plan |
| 3 | 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." |
| 4 | |
| 5 | |
| 6 | # Onboarding Plan Skill |
| 7 | |
| 8 | Creates a complete, structured onboarding plan tailored to a specific role — covering the first 90 days with clear milestones and success criteria. |
| 9 | |
| 10 | ## Required Inputs |
| 11 | **Role and level** of the new hire |
| 12 | **Team and manager** |
| 13 | **Key stakeholders** they will work with |
| 14 | **Top 3 priorities** for their first 90 days |
| 15 | **Tools and systems** they will need access to |
| 16 | **Company stage** (startup / scaleup / enterprise) |
| 17 | |
| 18 | ## Output Structure |
| 19 | |
| 20 | ### Onboarding Plan: [Name] — [Role] |
| 21 | **Start date:** [Date] | **Manager:** [Name] | **Buddy:** [Name] |
| 22 | |
| 23 | |
| 24 | |
| 25 | ### Before Day 1 (Manager checklist) |
| 26 | IT setup: laptop, accounts, email, Slack, key tools |
| 27 | Access provisioned to key systems |
| 28 | First week calendar blocked with key meetings |
| 29 | Buddy assigned and briefed |
| 30 | Welcome message sent with Day 1 logistics |
| 31 | |
| 32 | |
| 33 | |
| 34 | ### Week 1: Orient |
| 35 | Theme: Listen, learn, do not act yet. |
| 36 | |
| 37 | | Day | Focus | Key activities | |
| 38 | |---|---|---| |
| 39 | | Day 1 | IT setup, team intro | 1:1 with manager, team lunch | |
| 40 | | Day 2 | Product deep dive | Demo, key docs to read | |
| 41 | | Day 3 | Process and tools | Shadow key workflows | |
| 42 | | Day 4 | Stakeholder intros | 3-4 intro 1:1s | |
| 43 | | Day 5 | Week 1 debrief | Check-in, questions logged | |
| 44 | |
| 45 | **Week 1 milestone:** Can describe what the company does, the team role, and their top 3 priorities. |
| 46 | |
| 47 | |
| 48 | |
| 49 | ### Days 8-30: Learn |
| 50 | Learning goals: |
| 51 | Deep understanding of product from customer perspective |
| 52 | Know key metrics the team is measured on |
| 53 | Understand current projects and status |
| 54 | Map key stakeholder relationships |
| 55 | Complete all compliance/HR training |
| 56 | |
| 57 | **30-day milestone:** All stakeholder 1:1s complete. 2-3 early observations shared with manager. |
| 58 | |
| 59 | |
| 60 | |
| 61 | ### Days 31-60: Contribute |
| 62 | Goals: |
| 63 | Own at least one project end-to-end |
| 64 | Make one meaningful contribution |
| 65 | Build cross-functional relationships |
| 66 | Identify one process improvement |
| 67 | |
| 68 | **60-day milestone:** Delivered one tangible output. Manager says "this person is contributing." |
| 69 | |
| 70 | |
| 71 | |
| 72 | ### Days 61-90: Lead |
| 73 | Goals: |
| 74 | Operating independently on core responsibilities |
| 75 | Has formed and shared a point of view on priorities |
| 76 | Building reputation with key stakeholders |
| 77 | |
| 78 | **90-day milestone:** Ready for formal review. Clear 6-month plan in place. |
| 79 | |
| 80 | |
| 81 | |
| 82 | ### 90-Day Review Questions |
| 83 | Manager: Meeting expectations? What to double down on? What to develop? |
| 84 | New hire: Have the clarity, tools, support needed? What surprised you? What would you change about onboarding? |
| 85 | |
| 86 | ## Quality Checks |
| 87 | |
| 88 | [ ] Before Day 1 manager checklist is complete (IT, access, buddy, calendar) |
| 89 | [ ] Each phase (orient/learn/contribute/lead) has a clear milestone |
| 90 | [ ] 90-day review questions are included for both manager and new hire |
| 91 | [ ] Plan is tailored to the specific role and level (not generic) |
| 92 | [ ] Key stakeholder 1:1s are listed by name or role |
| 93 | |
| 94 | ## Anti-Patterns |
| 95 | |
| 96 | [ ] Do not produce a generic plan that could apply to any role — the plan must reference the specific role, team, tools, and priorities provided, not use placeholder text |
| 97 | [ ] Do not skip the Before Day 1 manager checklist — IT access and system provisioning failures on day 1 destroy first impressions and waste the new hire's first week |
| 98 | [ ] Do not set milestones without distinguishing between the orient, learn, contribute, and lead phases — collapsing phases produces plans where new hires are expected to lead before they understand the product |
| 99 | [ ] Do not omit the 90-day review questions — the review is the accountability mechanism for the entire plan, and skipping it makes the milestones meaningless |
| 100 | [ ] Do not treat the plan as a task list — each phase should have a clear theme and a milestone that describes an observable capability, not just a set of completed activities |
| 101 | |
| 102 | ## Example Trigger Phrases |
| 103 | "Create a 30/60/90 day plan for a new [role]" |
| 104 | "Write an onboarding plan for [name] starting as [role]" |
| 105 | "Build a first 90 days roadmap for our new hire" |
| 106 |
Discussion
Browse more free Claude skills or everything in Product.


