OpenParable
Skip to content
← Back to skills

Team Onboarding

Productivity
team-onboarding

Team Onboarding is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Comprehensive onboarding methodology for new team members covering pre-boarding through 90-day milestones. Use when planning onboarding, creating checklists, or establishing team integration processes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/business/team-onboarding/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/team-onboarding, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Team Onboarding

Pre-Onboarding

  • Create accounts (email, Slack, GitHub, AWS, etc.) with SSO/2FA
  • Prepare hardware, temporary credentials, password manager guide
  • Compile role-specific docs, update org charts
  • Configure calendar with initial meetings

Week 1: Orientation & Immersion

Day 1: Manager welcome, team intros, role expectations, IT setup, HR paperwork

Codebase:

  • Architecture overview and system diagrams
  • Main repos walkthrough with tech lead
  • Dev workflow, branching strategy, code style
  • CI/CD, deployment, monitoring tour

First Contributions:

  • "Good first issues" tasks
  • Pair programming on simple fix
  • Submit first PR with buddy guidance

Dev Environment Setup

  • IDE + extensions, linters, formatters, debugger, git config
  • Database connections (read-only initially), API keys via secrets manager
  • Container setup, testing framework, staging access

Buddy System

WeekFrequencyActivitiesTime
1DailyCheck-in, pair programming2 hrs/day
2-33x/weekCode review, architecture1 hr/day
42x/weekProject collaboration30 min/day
5-8WeeklyProgress check-in1 hr/week
9-12Bi-weeklyMentorship transition30 min/week

Milestones

30-Day

  • Complete mandatory training, merge 3+ PRs
  • Document one process, present learnings (10 min)

60-Day

  • Own small feature end-to-end, shadow on-call
  • Contribute to technical design, cross-team relationships

90-Day

  • Independent feature delivery, active code review
  • Mentor newer member, propose process improvement

Example Plans

Software Engineer (30/60/90)

Day 1-7: IT setup, team intros, dev env, first PR, architecture sessions Week 2-4: 5+ PR reviews as observer, shadow senior, document unclear process Day 31-60: Own first feature, design review, shadow on-call, pair with 3+ members Day 61-90: Lead small project, participate in planning, handle on-call with supervision

Senior/Lead Engineer (Accelerated)

Week 1: Leadership intros, full architecture deep-dive, priorities briefing, stakeholder meetings Week 2-3: Review postmortems, analyze tech debt, audit processes, identify quick wins Week 4: Lead first ceremony, own critical decision, establish 1:1 cadence, submit architectural proposal