Team Onboarding Playbook
Skill Verifiziert AktivDesign 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.
To create predictable and efficient onboarding experiences that get new team members productive quickly and effectively.
Funktionen
- Structured 30-60-90 day onboarding plans
- Framework for belonging, context, contribution, and mastery
- Role-specific onboarding overlays
- Detailed pre-day-1 preparation checklists
- Guidance on failure patterns and retrospective updates
Anwendungsfälle
- Onboarding new hires when no formal plan exists
- Ramping up contractors or agency partners
- Capturing critical tribal knowledge from departing team members
- Improving chaotic or slow existing onboarding processes
Nicht-Ziele
- Ongoing performance management
- Training on specific technologies
- General documentation strategy
- Role definition or hiring processes
Workflow
- Start the playbook before the new person arrives.
- Pre-stage accounts, hardware, and access.
- Assign a buddy and provide guidance.
- Send welcome message and day-1 schedule.
- Focus week 1 on belonging and context.
- Check in daily first week, weekly first month.
- Run formal 30/60/90 milestone check-ins.
- Conduct a retrospective after 90 days to update the playbook.
Praktiken
- Onboarding process design
- Team development
- Knowledge transfer
Voraussetzungen
- Role definition for the new hire
- Existing team artifacts (docs, code, etc.)
- Defined team structure and mentors
- Information on required tools and access
Installation
npx skills add rampstackco/claude-skillsFührt das Vercel skills CLI (skills.sh) via npx aus — benötigt Node.js lokal und mindestens einen installierten skills-kompatiblen Agent (Claude Code, Cursor, Codex, …). Setzt voraus, dass das Repo dem agentskills.io-Format folgt.
Qualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Interview System Designer
100This skill should be used when the user asks to "design interview processes", "create hiring pipelines", "calibrate interview loops", "generate interview questions", "design competency matrices", "analyze interviewer bias", "create scoring rubrics", "build question banks", or "optimize hiring systems". Use for designing role-specific interview loops, competency assessments, and hiring calibration systems.
Codebase Onboarding
100Codebase Onboarding
Onboard
100/cs:onboard — Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents.
Drive Motivation
100Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "team incentives", "autonomy", "mastery", "purpose-driven", "employee engagement", or "reward systems". Also trigger when designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.
Culture Architect
99Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions culture, values, culture debt, founder culture, or culture code.
Interactive Product Tour
99Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of need), and contextual-when-needed (surfaces help at the moment friction occurs) patterns. Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform. Also triggers when feature adoption is low, when users miss key product capabilities, or when an in-product help system is being scoped for the first time.