onboarding-new-hires

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill onboarding-new-hires
0 commentsdiscussion
summary

Structured 30-60-90 day onboarding framework drawing from 14 product leaders' approaches.

  • Covers listening tours, milestone planning, early wins, and belonging through pairing rather than isolation on day one
  • Emphasizes defining success at 90 days, 1 year, and 2 years before onboarding begins, plus identifying golden rituals to teach by first Friday
  • Includes relationship design conversations, documented management philosophy, and early ownership assignment to accelerate ramp-up to 30
skill.md

Onboarding New Hires

Help the user onboard new team members effectively using approaches from 14 product leaders.

How to Help

When the user asks for help with onboarding:

  1. Understand the context - Ask if they're onboarding someone or being onboarded, the seniority level, and whether it's a new role or backfill
  2. Design the structure - Help them create a 30-60-90 day plan with clear milestones and success criteria
  3. Prioritize belonging and learning - Ensure the plan includes social integration, not just tasks
  4. Engineer early wins - Identify opportunities for the new hire to demonstrate value quickly

Core Principles

Listen first, act later - diagnose before you treat

Deb Liu: "The first 90 days are focused on listening and learning first, then doing. Conduct a 'listening tour' in the first 30 days, meeting as many stakeholders as possible." Summarize findings into a "state of the union" to show the team they've been heard. Align on vision in days 30-60, move to full execution by day 90.

Define success at 90 days, 1 year, and 2 years

Lauren Ipsen: "The 90-day plan is overused but necessary, and that's just the tip of the iceberg. What should this person be doing a year from now? Two years from now?" Define what "crushing it" looks like at each milestone before starting the search.

Create immediate belonging through pairing

Heidi Helfand: "Help them feel a sense of belonging by not having their first day be them sitting alone. Have someone be a 'first pair.'" Ensure new hires are not working alone on day one. Assign a buddy to work with them immediately. Encourage sharing personal stories to build connection.

Teach golden rituals by the first Friday

Shishir Mehrotra: "Great companies have a very small list of golden rituals. Every employee knows them by their first Friday." Include core company rituals in the onboarding curriculum. These rituals should be named, known, and templated.

Engineer early wins for visibility

Melissa Tan: "How do I help them secure early wins? I'll suggest 'You should do this presentation - it's a great way to get visibility early.'" Identify low-hanging fruit projects for new hires. Create opportunities for them to present to leadership in their first weeks.

Document your philosophy publicly

Brandon Chu: "People joining my team already knew how I thought because they'd Google me. It passively onboarded a lot of the PMs." Write about your management and product philosophy. New hires can ramp up before their first day.

Have a "relationship design" conversation

Kenneth Berger: "For maybe your first 10-20 employees, have a relationship design conversation when they're hired." Collaboratively figure out the best way to work together given specific roles and personalities. This prevents friction and "out of integrity" behavior later.

Don't overpromise during hiring

Molly Graham: "Do not promise things you can't control. Be honest about the ambiguity and chaos of a scaling environment." Avoid promising stability, specific titles, or career paths you can't guarantee. Overpromises become "letter bombs" that demoralize high performers when they explode.

Accelerate ownership with clear cadences

Timothy Davis: "I want to try and make onboarding 30-45 days by giving them responsibility early. Here's everything we did, here's your responsibilities, go." Use an ops cadence spreadsheet to define task frequency. Assign campaign or project ownership within the first few weeks.

Use AI for low-friction knowledge access

Scott Wu: "New engineers can ask Devin questions about the codebase. It's nice to be able to ask without social pressure." AI tools can help new hires explore internal systems and ask "dumb questions" without feeling judged.

Questions to Help Users

  • "What does success look like at 30, 60, and 90 days for this person?"
  • "Who is their 'first pair' or buddy on day one?"
  • "What are the company's golden rituals they need to know by their first Friday?"
  • "What early win can we engineer to give them visibility and credibility?"
  • "Have you documented your philosophy anywhere they can read before starting?"
  • "What did you promise them during hiring that you need to deliver on?"

Common Mistakes to Flag

  • No structured 90-day plan - New hires need clear milestones. "Figure it out" is not onboarding
  • Leaving them alone on day one - Isolation kills belonging. Assign a pair from the start
  • All tasks, no relationships - Onboarding is social, not just functional. Prioritize introductions and connection
  • Delayed ownership - Don't wait months to give responsibility. Find ways to assign ownership in weeks
  • Over-promising during hiring - Be honest about chaos and ambiguity. Broken promises demoralize

Deep Dive

For all 14 insights from 14 guests, see references/guest-insights.md

Related Skills

  • Writing Job Descriptions
  • Conducting Interviews
  • Building Team Culture
  • Running Effective 1:1s
how to use onboarding-new-hires

How to use onboarding-new-hires on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add onboarding-new-hires
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill onboarding-new-hires

The skills CLI fetches onboarding-new-hires from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/onboarding-new-hires

Reload or restart Cursor to activate onboarding-new-hires. Access the skill through slash commands (e.g., /onboarding-new-hires) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.642 reviews
  • Ira Tandon· Dec 28, 2024

    We added onboarding-new-hires from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sophia Farah· Dec 20, 2024

    Registry listing for onboarding-new-hires matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ganesh Mohane· Dec 12, 2024

    Keeps context tight: onboarding-new-hires is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Amelia Johnson· Nov 11, 2024

    Keeps context tight: onboarding-new-hires is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Rahul Santra· Nov 3, 2024

    Registry listing for onboarding-new-hires matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Pratham Ware· Oct 22, 2024

    onboarding-new-hires reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Layla Khan· Oct 2, 2024

    onboarding-new-hires is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aarav Flores· Sep 21, 2024

    Solid pick for teams standardizing on skills: onboarding-new-hires is focused, and the summary matches what you get after install.

  • Sakshi Patil· Sep 13, 2024

    I recommend onboarding-new-hires for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aarav Patel· Sep 13, 2024

    Useful defaults in onboarding-new-hires — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 42

1 / 5