onboarding-plan

$npx mdskill add mohitagw15856/pm-claude-skills/onboarding-plan

Creates a complete, structured onboarding plan tailored to a specific role — covering the first 90 days with clear milestones and success criteria.

SKILL.md

.github/skills/onboarding-planView on GitHub ↗
---
name: onboarding-plan
description: "Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria."
---

# Onboarding Plan Skill

Creates a complete, structured onboarding plan tailored to a specific role — covering the first 90 days with clear milestones and success criteria.

## Required Inputs
- **Role and level** of the new hire
- **Team and manager**
- **Key stakeholders** they will work with
- **Top 3 priorities** for their first 90 days
- **Tools and systems** they will need access to
- **Company stage** (startup / scaleup / enterprise)

## Output Structure

### Onboarding Plan: [Name] — [Role]
**Start date:** [Date] | **Manager:** [Name] | **Buddy:** [Name]

---

### Before Day 1 (Manager checklist)
- IT setup: laptop, accounts, email, Slack, key tools
- Access provisioned to key systems
- First week calendar blocked with key meetings
- Buddy assigned and briefed
- Welcome message sent with Day 1 logistics

---

### Week 1: Orient
Theme: Listen, learn, do not act yet.

| Day | Focus | Key activities |
|---|---|---|
| Day 1 | IT setup, team intro | 1:1 with manager, team lunch |
| Day 2 | Product deep dive | Demo, key docs to read |
| Day 3 | Process and tools | Shadow key workflows |
| Day 4 | Stakeholder intros | 3-4 intro 1:1s |
| Day 5 | Week 1 debrief | Check-in, questions logged |

**Week 1 milestone:** Can describe what the company does, the team role, and their top 3 priorities.

---

### Days 8-30: Learn
Learning goals:
- Deep understanding of product from customer perspective
- Know key metrics the team is measured on
- Understand current projects and status
- Map key stakeholder relationships
- Complete all compliance/HR training

**30-day milestone:** All stakeholder 1:1s complete. 2-3 early observations shared with manager.

---

### Days 31-60: Contribute
Goals:
- Own at least one project end-to-end
- Make one meaningful contribution
- Build cross-functional relationships
- Identify one process improvement

**60-day milestone:** Delivered one tangible output. Manager says "this person is contributing."

---

### Days 61-90: Lead
Goals:
- Operating independently on core responsibilities
- Has formed and shared a point of view on priorities
- Building reputation with key stakeholders

**90-day milestone:** Ready for formal review. Clear 6-month plan in place.

---

### 90-Day Review Questions
Manager: Meeting expectations? What to double down on? What to develop?
New hire: Have the clarity, tools, support needed? What surprised you? What would you change about onboarding?

## Quality Checks

- [ ] Before Day 1 manager checklist is complete (IT, access, buddy, calendar)
- [ ] Each phase (orient/learn/contribute/lead) has a clear milestone
- [ ] 90-day review questions are included for both manager and new hire
- [ ] Plan is tailored to the specific role and level (not generic)
- [ ] Key stakeholder 1:1s are listed by name or role

## Example Trigger Phrases
- "Create a 30/60/90 day plan for a new [role]"
- "Write an onboarding plan for [name] starting as [role]"
- "Build a first 90 days roadmap for our new hire"

More from mohitagw15856/pm-claude-skills

SkillDescription
360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.