rampstackco/claude-skills / skills/team-onboarding-playbook
team-onboarding-playbook
VerifiedDesign 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 365 B |
| SKILL.md | skill md | 8.9 KB |
| references/onboarding-checklist.md | markdown | 6.8 KB |
references/onboarding-checklist.md
View on GitHub# Onboarding checklist
A day-by-day, week-by-week checklist for the first 30 days. Adapt the role-specific items to fit your team.
## Before day 1 (1 week ahead)
Manager prep:
- [ ] Confirm start date and any logistics (remote, hybrid, in-office).
- [ ] Assign onboarding buddy. Brief them on expectations.
- [ ] Order hardware. Confirm delivery before start date.
- [ ] Create accounts: email, chat, source control, design tools, project management, calendar, password manager.
- [ ] Add to relevant team channels and meeting invites.
- [ ] Block manager calendar for daily check-ins in week 1.
- [ ] Send welcome email to new hire 3-5 days before start. Include: day-1 logistics, what to expect, where to be, what to bring.
- [ ] Notify the team via channel: who is starting, when, what role.
- [ ] Prep first task. Something small, scoped, shippable in week 1 or 2.
## Day 1
Morning:
- [ ] Welcome from manager (30 min, not 90 min).
- [ ] Tour of tools, accounts, and where things live.
- [ ] Lunch with buddy or team (whatever is normal for your team).
Afternoon:
- [ ] Read the welcome doc or onboarding hub.
- [ ] Set up local environment. Buddy or buddy-channel available for help.
- [ ] First commit, design upload, doc edit, or equivalent. Trivial. Just to validate the workflow.
End of day:
- [ ] 15-minute check-in with manager. How did it go.
## Week 1
Goals: belonging and basic context. Not productivity.
- [ ] Daily 15-minute check-in with manager.
- [ ] 1:1 with buddy at least twice.
- [ ] Read the curated reading list (5-10 docs, no more).
- [ ] Meet with 5-7 people they will work with. 30 minutes each. Casual.
- [ ] Attend team standup and one team meeting (without obligation to contribute).
- [ ] Submit at least one trivial fix or improvement (typo, doc clarification, small refactor).
- [ ] Set up time tracking, expense, or admin systems if your org uses them.
- [ ] Confirm hardware, software, and access are all working.
End of week 1:
- [ ] Manager check-in: what is unclear, what felt wrong, what is missing.
## Week 2
Goals: contributing to real work, even in a small way.
- [ ] Pair with a teammate on a real task. Half day to a full day.
- [ ] Take ownership of the first small task. Should be shippable in 3-5 days.
- [ ] Attend customer call, support sync, or equivalent customer touchpoint.
- [ ] Read the recent decision log or major PRDs from the last 3 months.
- [ ] First contribution to standups: what they are working on.
End of week 2:
- [ ] Manager check-in: how is the first task going. What is blocking. What feels overwhelming.
## Week 3
Goals: independent ownership starts.
- [ ] Ship the first small task.
- [ ] Take on a slightly larger task. 1-2 weeks of work.
- [ ] Participate in code review, design critique, or equivalent.
- [ ] Meet with 3-5 cross-functional partners (PM ↔ Eng, Design ↔ PM, etc.).
- [ ] Begin to recognize patterns: "this is the third time someone asked X, where is that documented?"
End of week 3:
- [ ] Buddy check-in: how is the experience. What is the new hire stuck on that they will not raise to the manager.
## Week 4 / 30-day mark
Goals: validate the ramp is on track.
- [ ] Complete the first medium-sized project or be visibly in flight.
- [ ] Have a working mental model of the product, team, and stack.
- [ ] Have at least one improvement filed (a doc fix, process suggestion, automation).
- [ ] Manager 30-day review (see template below).
## 30-day review
Manager runs this with the new hire, in 1:1, around day 30.
```
30-day review for [name]
What is going well:
- [Two or three things]
What is unclear or hard:
- [Two or three things]
What I have shipped or contributed to:
- [List]
What I want to be doing more of:
- [List]
What I want help with:
- [List]
Manager observations:
- [What you have noticed]
Action items:
- [Specific things to address before 60-day mark]
```
The output of the 30-day review is honest signal. If the new hire is behind, the manager addresses the cause, not the symptom. If they are ahead, accelerate.
## 60-day milestones
By day 60:
- [ ] Owning a project or area independently.
- [ ] Asking targeted questions, not "how does anything work" questions.
- [ ] Has working relationships outside the immediate team.
- [ ] Has been on customer or user calls if applicable.
- [ ] Has flagged at least one process improvement.
- [ ] 60-day review complete.
## 90-day milestones
By day 90:
- [ ] Fully productive in the role at expected level.
- [ ] Participating in planning and roadmap discussions.
- [ ] On call or on rotation if the team has one.
- [ ] Capable of teaching parts of the system to a peer.
- [ ] Has identified gaps in onboarding from their perspective.
- [ ] 90-day review and onboarding retrospective complete.
## 90-day onboarding retrospective
Run this with the new hire at the end of 90 days. Capture the answers. Update the playbook.
```
What was great about your onboarding:
- [List]
What was confusing or hard:
- [List]
What was missing:
- [List]
What you would have liked on day 1:
- [List]
What you would change for the next person:
- [List]
What you wish you had known earlier:
- [List]
```
The output of this retro feeds the next version of the playbook. Without this loop, every new hire faces the same gaps.
## Role-specific first tasks
Examples of good first tasks (shippable in week 1-2):
### Engineering
- Fix a small bug from the bug tracker (not customer-blocking, but real).
- Add a missing test or improve a flaky one.
- Update a deprecated API call in one place.
- Improve a developer doc that has been out of date.
### Design
- Audit a small part of the product against the design system.
- Design an empty state, error state, or settings sub-page.
- Update an outdated illustration or asset.
- Document a component that is in production but not in the design system.
### Product
- Write a competitive analysis on one feature area.
- Document a customer pain point heard in support.
- Update a stale PRD with current state.
- Write a one-pager on a roadmap item that needs sharper framing.
### Marketing / Content
- Edit and update a stale blog post.
- Audit recent campaign performance and write a 1-page summary.
- Repurpose an existing piece of content into a new format.
- Write a short customer quote roundup or testimonial summary.
The pattern: real, scoped, ships in days, low risk, builds context.
## What "fully ramped" looks like
A new hire is fully ramped when:
- They no longer ask "how does this work" but "why was it built this way".
- They contribute to direction, not just execution.
- They identify gaps and fill them without being asked.
- They mentor or assist the next new hire.
- They push back on things that do not make sense.
This usually lands somewhere between 90 and 180 days, depending on the role and the system's complexity. Track it. If 180 days passes and the person is still not at this bar, dig into why.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |