Skill

Skill: onboarding-plan

Create a structured 30/60/90-day onboarding plan for a new team member joining a delivery team — so they ramp up fast and contribute confidently.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-toolkit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create a structured 30/60/90-day onboarding plan for a new team member joining a delivery team — so they ramp up fast and contribute confidently.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: onboarding-plan

Purpose

Create a structured 30/60/90-day onboarding plan for a new team member joining a delivery team — so they ramp up fast and contribute confidently.

When to Use

New developer, QA, designer, or PDM joining the team
Contractor or vendor resource starting
New PDM inheriting an existing programme

Framework: 30/60/90-Day Onboarding Plan

Step 1 — Gather Context

Ask for:

Role and seniority
Current project / release state
Key people they need to know
Tools and systems they need access to

Day 1–5: Access and Orientation

Goals: Set up, oriented, and welcomed

Accounts created: Jira, Confluence, Slack, GitHub, etc.
Intro meetings: Team, PDM, Tech Lead, QA Lead
Read: Team charter, working agreements, DoD
Shadowed: one standup, one sprint planning or sync meeting
Assigned: one low-complexity buddy task

30-Day Goals: Learn the System

Goal	How	Done By
Understand current release scope	Read release plan + dependency map	Day 10
Know the tech stack	Tech Lead walkthrough	Day 15
Contribute first task independently	Low-complexity story	Day 20
Know who to go to for what	RACI + 1:1s with key people	Day 30

60-Day Goals: Contribute Reliably

Goal	How	Done By
Own a sprint story end-to-end	Sprint assignment	Day 45
Participate in Three Amigos	Join session	Day 50
Flag blockers independently	Daily standup	Ongoing
Complete onboarding feedback	Survey	Day 60

90-Day Goals: Operate Independently

Goal	How	Done By
Contribute to sprint planning	Active participant	Day 75
Identify one process improvement	Retrospective	Day 90
1:1 progress check with PDM	Review goals	Day 90

Check-In Questions (30/60/90 Reviews)

What's going well?
What's unclear or confusing?
Where do you feel least confident?
What would help you most right now?

Output Format

Day 1–5 checklist
30/60/90-day goal table
Check-in question set
Suggested next command: /working-agreements or /raci-matrix