team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also triggers when one person owns all the tribal knowledge and you need to capture it, when you keep losing people in their first 90 days, or when a new project has many fresh members joining at once. Useful for engineering, design, product, marketing, and operations roles.
Profile →npx skills add rampstackco/claude-skills --skill team-onboarding-playbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
A repeatable framework for building an onboarding playbook that ramps new team members predictably without burning out the people training them. ## When to use - A new hire is joining and you do not have a written onboarding plan. - An existing onboarding process is informal and inconsistent. - A team is growing fast and onboarding is the bottleneck. - A contractor or agency partner needs to ramp up quickly. - A team member is leaving and their knowledge needs capturing. - Onboarding currently takes too long and you want to reduce it. ## When NOT to use - For ongoing performance management (different problem). - For training on a specific technology (use targeted docs and tutorials). - For documentation strategy in general (use `documentation-strategy`). - For role definition or hiring (different upstream problem). ## Required inputs - The role: what the person will do, what success looks like at 90 days. - Existing artifacts: docs, runbooks, codebases, design files. - The team: who will mentor, who will pair, who answers what kind of question. - Tools and access: what accounts and systems the new person needs. - Time budget: how much time team members can invest in onboarding. ##
- When to use
- When NOT to use
- Required inputs
- The framework
- Layer 1: Belonging (Day 1 to Week 1)
- Layer 2: Context (Week 1 to Week 4)
- Layer 3: Contribution (Week 2 to Week 6)
- Layer 4: Mastery (Month 2 to Month 3)
- The 30/60/90 plan
- 30 days
- 60 days
- 90 days
- The role-specific overlay
- Engineering
What does the team-onboarding-playbook skill do?
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also triggers when one person owns all the tribal knowledge and you need to capture it, when you keep losing people in their first 90 days, or when a new project has many fresh members joining at once. Useful for engineering, design, product, marketing, and operations roles.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill team-onboarding-playbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.