Individual skill
onboarding-plan-builder
Produces a 30/60/90-day onboarding plan for a specific role with phased milestones, first-week setup, observable success criteria, and ramp reviews. Use when a new hire has an accepted offer or start date, or when asked to write, draft, or improve a 30/60/90 / ramp / onboarding plan for a role. Do NOT use for the structure of ongoing recurring 1:1s - use 1on1-agenda instead.
skills/onboarding-plan-builder/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,783 bytes
Read excerpt
# Onboarding Plan Builder
Turn "get up to speed" into a sequenced, role-specific 30/60/90-day plan with concrete milestones and observable success criteria.
## Workflow
1. Capture the inputs. Pull the role's actual outcomes, level, team, manager, and start date. If the role's outcomes are unstated, ask for them or derive them from the job description before building - never plan against a generic title.
2. Phase the 90 days by cognitive load: Learn (0-30), Contribute (31-60), Own (61-90). Day 30 targets understanding systems, people, and context; day 60 targets shipping scoped work with support; day 90 targets owning an area with autonomy.
3. Attach 2-4 milestones to each phase, drawn from the role's real outcomes (not a generic checklist). Order milestones so each depends only on what earlier phases delivered.
4. Specify the first week concretely: access and tools provisioned before day one, the named buddy/onboarding partner, who to meet and why, where the docs live, and one small first task that produces a real win.
5. Write an observable success criterion per milestone - what "on track" looks like in evidence ("merged first PR," "ran a customer call solo," "presented the area roadmap"), never a feeling.
6. Define the three ramp reviews (day 30, 60, 90). Each covers progress vs. milestones, blockers, support needed, and a two-way fit check that invites feedback on the onboarding itself. Reference that recurring 1:1s exist; do not design their agenda here.
7. List the relationships and context to build: key cross-functional partners, rituals to join, and the implicit norms a newcomer cannot infer.
8. Calibrate to role and level, and flag where accommodations, visa, or relocation timing may shift the schedule.
