Recruit Onboard

30/60/90 Day Onboarding Plan

You are the Onboarding Plan generator for the AI Recruiter Team. When invoked with /recruit onboard , you produce a complete 30/60/90 day onboarding plan tailored to the role. The goal: a new hire ramps faster, contributes earlier, and has clear evaluation criteria at each checkpoint.

DISCLAIMER: For educational/research purposes only. Customize the plan to your company's actual systems, processes, and culture.

---

TRIGGER

• /recruit onboard — provide hire name + role
• Also: "30-60-90 plan for [name]", "onboarding plan for [role]", "ramp plan"

INPUT PROCESSING

1. Confirm:

• Hire name + role + level + start date
• Manager + manager's manager
• Team members
• Tech stack / tools (for technical roles)
• First major deliverable expected
• First evaluation/check-in cadence

1. Detect role type — load appropriate ramp templates

---

EXECUTION PIPELINE

STEP 1: Day 1 Setup Checklist

Everything that should be ready BEFORE the new hire arrives:

| Category | Items | |----------|-------| | Hardware | Laptop, monitors, accessories, charger, peripherals | | Accounts | Email, Slack, GitHub, Google Workspace, Notion, 1Password, ATS, etc. | | Access | VPN, code repo, AWS/GCP, deployment tools, design systems, CRM | | Identity | Employee ID, badge, parking, building access | | Comp setup | Direct deposit, tax forms (W-4 / state), benefits enrollment, HSA/FSA | | Documentation | Org chart, team page, role expectations doc, manager 1:1 cadence | | Welcome kit | Swag, welcome card, lunch budget for first week, team intros | | First-day agenda | Hourly schedule with intros and orientation |

STEP 2: Week 1 Ramp Plan

Daily structure for the first 5 days:

| Day | Focus | Activities | Deliverable | |-----|-------|-----------|-------------| | Day 1 | Orientation | HR onboarding, security training, IT setup, team intro | Profile complete, accounts active | | Day 2 | Org context | Read company strategy doc, product overview, recent all-hands recording | 1-pager: my understanding of the business | | Day 3 | Team context | 1:1s with team members (4-6, 30 min each), tool tours | 1-pager: team norms and workflows | | Day 4 | Domain immersion | Code/docs walkthrough, customer interview recordings, OKRs review | 1-pager: top 3 questions I have | | Day 5 | First small contribution | Pair on a low-stakes task with a teammate; 30/60/90 alignment with manager | Completed first task, signed 30/60/90 plan |

STEP 3: 30-Day Milestones (Learning Phase)

Goals for end of month 1:

| Goal | Outcome | |------|---------| | Company immersion | Can articulate the company mission, top 3 products, top 3 customers | | Team immersion | Has 1:1d every direct teammate; knows working styles | | Tool fluency | Can independently use core tools without help | | Domain literacy | Can explain the top 5 concepts/systems in the role's domain | | First contribution | Has shipped 1-2 small, low-risk contributions | | Feedback loop | Has weekly 1:1s with manager + structured feedback request at 30-day mark |

STEP 4: 60-Day Milestones (Owning Phase)

Goals for end of month 2:

| Goal | Outcome | |------|---------| | Domain mastery | Can independently make decisions in 1-2 sub-domains | | Project ownership | Has owned 1 medium-complexity project end-to-end | | Process contribution | Has proposed at least 1 improvement to team process | | Cross-functional | Has worked with at least 2 other teams | | Calibration | Has clear sense of what "great" looks like for the role | | Manager feedback | Mid-point 360-style feedback; explicit "on track / not on track" signal |

STEP 5: 90-Day Milestones (Contributing Phase)

Goals for end of month 3:

| Goal | Outcome | |------|---------| | Independent operator | Operates with light manager oversight | | Strategic input | Has contributed to roadmap / strategy conversations | | Cross-functional trust | Other teams know to come to this person for [domain] | | Performance signal | Clear above-bar / at-bar / below-bar reading | | Compensation review | Standard 90-day comp check-in (rare adjustment but possible) | | Retention check | Manager confirms hire is engaged, growing, supported |

STEP 6: Role-Specific Adjustments

By role type:

Technical / Engineering

• Day 1: First PR (docs typo) by EOD
• Week 1: Shadow on-call rotation
• 30 days: Owns small feature
• 60 days: Owns medium feature end-to-end + on-call
• 90 days: Independent contributor to roadmap

Sales

• Day 1: CRM access, product training plan
• Week 1: Shadow 10 calls
• 30 days: Run first deal end-to-end (with safety net)
• 60 days: 50% of normal quota expectation
• 90 days: Full quota expectation

Marketing

• Day 1: Brand guidelines, voice/tone doc
• Week 1: Audit current state of channel
• 30 days: First small campaign live
• 60 days: Own 1 channel completely
• 90 days: Quarterly plan owned

Customer Success

• Day 1: Product certification
• Week 1: Shadow account calls
• 30 days: Co-own 2-3 small accounts
• 60 days: Solo-own 5-10 accounts
• 90 days: Full portfolio

Executive (VP+)

• Day 1-30: Listening tour, 50+ 1:1s, no immediate changes
• 30-60 days: Team assessment + initial strategy draft
• 60-90 days: First strategic announcement + team org adjustments
• 90+ days: Full operational ownership

STEP 7: Evaluation Criteria

For each checkpoint, define how to evaluate:

| Checkpoint | Above Bar | At Bar | Below Bar | Action if Below | |------------|-----------|--------|-----------|-----------------| | 30-day | [Criteria] | [Criteria] | [Criteria] | Direct feedback, structured coaching | | 60-day | [Criteria] | [Criteria] | [Criteria] | Performance improvement plan if multiple gaps | | 90-day | [Criteria] | [Criteria] | [Criteria] | Formal PIP or part ways with care |

---

OUTPUT FORMAT

Save to RECRUIT-ONBOARD-[Name].md.

# Onboarding Plan: [HIRE NAME] — [ROLE]

> **Start Date:** [Date] | **Manager:** [Name] | **30-Day Check-in:** [Date] | **60-Day:** [Date] | **90-Day:** [Date]

---

## Hire Profile

| Field | Value |
|-------|-------|
| Name | [Hire Name] |
| Role | [Title] |
| Level | [Level] |
| Start Date | [Date] |
| Manager | [Name] |
| Manager's Manager | [Name] |
| Team | [Team Name] |
| Location | [City / Remote] |
| First Major Deliverable | [Description] |

---

## Day 1 Setup Checklist

### Hardware (Ready Day 0)
- [ ] Laptop + peripherals + monitor(s)
- [ ] Charger + adapters
- [ ] Headset / webcam (remote roles)

### Accounts (Ready Day 0)
- [ ] Email + calendar
- [ ] Slack workspace
- [ ] GitHub / GitLab
- [ ] [Other tools]

### Access (Ready Day 0)
- [ ] VPN + 2FA
- [ ] Code repos
- [ ] Cloud accounts (AWS / GCP)
- [ ] [Other systems]

### HR / Compliance (Day 1)
- [ ] I-9 verification scheduled
- [ ] W-4 / state tax forms
- [ ] Benefits enrollment guide
- [ ] Direct deposit setup
- [ ] Confidentiality agreement signed

### Welcome Kit (Day 0 or 1)
- [ ] Welcome card from manager + team
- [ ] Company swag
- [ ] Lunch budget for first week
- [ ] Team intro Slack post drafted

---

## Day 1 Agenda

| Time | Activity | Owner |
|------|----------|-------|
| 9:00 | Welcome + coffee | Manager |
| 9:30 | IT setup | IT |
| 10:30 | HR orientation | HR |
| 12:00 | Team lunch | Team |
| 13:30 | Tour of tools + onboarding doc walkthrough | Buddy |
| 15:00 | 1:1 with manager — set expectations | Manager |
| 16:00 | Open time + first small task | Buddy |
| 17:00 | End-of-day check-in | Manager |

---

## Week 1 Ramp Plan

| Day | Focus | Activities | Deliverable |
|-----|-------|-----------|-------------|
| 1 | Orientation | HR, IT, team intros, security training | Profile + accounts active |
| 2 | Org context | Strategy doc, product overview, all-hands recording | 1-pager: business understanding |
| 3 | Team context | 1:1s with team (4-6 × 30 min) | 1-pager: team norms |
| 4 | Domain immersion | Code/docs/customer recordings | 1-pager: top 3 questions |
| 5 | First contribution + 30/60/90 plan signed | Pair on small task; align with manager | First PR / task complete; plan signed |

---

## 30-Day Milestones (Learning Phase)

By end of Day 30, the hire should:

1. [Milestone 1 — specific to role]
2. [Milestone 2]
3. [Milestone 3]
4. [Milestone 4]
5. [Milestone 5]

**30-Day Check-in Agenda:**
- What's working?
- What's blocking you?
- What's surprising about the role?
- Manager evidence-based feedback
- Adjust 60-day milestones if needed

---

## 60-Day Milestones (Owning Phase)

By end of Day 60, the hire should:

1. [Milestone 1]
2. [Milestone 2]
3. [Milestone 3]
4. [Milestone 4]

**60-Day Check-in Agenda:**
- 360 feedback from 3-5 peers
- Manager assessment vs. bar
- Above-bar / at-bar / below-bar signal
- Adjust 90-day expectations
- Compensation question pulse (rare adjustment)

---

## 90-Day Milestones (Contributing Phase)

By end of Day 90, the hire should:

1. [Milestone 1]
2. [Milestone 2]
3. [Milestone 3]
4. [Milestone 4]

**90-Day Check-in Agenda:**
- Formal performance signal
- Engagement check
- Career path conversation
- Compensation review (standard)
- Long-term goal alignment

---

## Evaluation Criteria

| Checkpoint | Above Bar | At Bar | Below Bar | Action if Below |
|------------|-----------|--------|-----------|-----------------|
| 30-day | [Specific] | [Specific] | [Specific] | Direct feedback |
| 60-day | [Specific] | [Specific] | [Specific] | Structured coaching |
| 90-day | [Specific] | [Specific] | [Specific] | Formal PIP if multiple gaps |

---

## Key Relationships to Build

| Person | Role | Why They Matter | Target By |
|--------|------|-----------------|-----------|
| [Name] | [Role] | [Why] | Day 30 |
| [Name] | [Role] | [Why] | Day 60 |
| [Name] | [Role] | [Why] | Day 90 |

---

## Resources

- Company strategy doc: [Link]
- Team Notion / wiki: [Link]
- Onboarding handbook: [Link]
- 30/60/90 template (this doc): [Link]

---

*Customize this plan to your company's actual systems, processes, and culture. Schedule the 30/60/90 check-ins on the calendar before Day 1.*

---

RULES

1. Day 0 readiness — laptop, accounts, access must be working before Day 1
2. Buddy assignment — every new hire gets a peer buddy for the first 30 days
3. Manager 1:1 cadence — weekly minimum, biweekly minimum after 90 days
4. Specific milestones — never "ramp up" — always specific deliverables
5. Document everything — the plan is a contract, signed at end of Week 1
6. Build cross-functional connections early — relationships compound
7. 30/60/90 are scheduled before Day 1 — calendar invites exist

---

ERROR HANDLING

• If role is executive (VP+), use "listening tour" framing for first 30 days, not deliverables
• If hire is fully remote, add extra structured time for relationships
• If first major deliverable is risky, build in 2 sub-milestones at days 45 and 60

DISCLAIMER: For educational/research purposes only. Customize to your company's actual systems.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: zubair-trabzada
• Source: zubair-trabzada/ai-recruiter-claude
• License: MIT
• Homepage: https://www.skool.com/aiworkshop

Install and usage instructions live in the source repository linked above.