eng-dev-onboarding

Generate personalized developer onboarding plans with environment setup and milestones.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-dev-onboarding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eng-dev-onboarding
Source: https://github.com/viditparashar96/second-brain-claude/tree/main/skills/eng-dev-onboarding
Command: npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-dev-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New hires often struggle to become productive because onboarding is generic, lacks product context, and misses clear environment setup, starter tasks, and milestone check-ins. This Skill creates a personalized, product-aware ramp plan that aligns role, level, and product tech stack so engineers can contribute quickly and safely.

Core Features & Use Cases

  • Profile-driven plans: Collects name, role, level, product assignment, start date, and buddy to tailor the plan.
  • Product-aware environment setup: Extracts tech stack and architecture from PRODUCTS.md and project docs to generate accurate setup steps.
  • Milestones & tracking: Produces week-by-week starter tasks and 30/60/90 milestones, creates calendar check-ins, saves a local onboarding doc, and logs a summary to memory for continuous improvement.
  • Use Case: Ramp a mid-level frontend engineer onto the payments product with a first-week environment checklist, three starter PR tasks, and 30/60/90 check-ins.

Quick Start

Use the eng-dev-onboarding skill to generate a product-aware 30/60/90 day onboarding plan for [developer-name] assigned to [product] with role [role] and level [junior|mid|senior], then save it to docs/onboarding/{name-slug}.md.

Frequently Asked Questions about eng-dev-onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a 30/60/90 day developer onboarding plan for a new engineer?▼

A 30/60/90 day developer onboarding plan is generated by collecting the new hire's name, role, level, and product assignment to produce role-adjusted first-week schedules, starter tasks, and milestone check-ins. You need product documentation like PRODUCTS.md and README to ensure the plan is product-aware.

What is a product-aware developer ramp-up plan and how does it work?▼

A product-aware developer ramp-up plan extracts the tech stack and architecture from project documentation like PRODUCTS.md and ORG.md to generate accurate environment setup steps and starter PR tasks. This ensures new engineers contribute quickly and safely to a specific codebase.

Can I generate starter tasks and environment setup checklists for a mid-level frontend engineer onboarding?▼

Yes, profile-driven onboarding plans tailor starter tasks and environment setup checklists based on the engineer's role and level. A mid-level frontend engineer receives a customized first-week schedule with specific environment configuration steps and starter PR tasks.

Do I need product documentation to generate a personalized developer onboarding schedule?▼

Yes, product documentation is required to generate a personalized developer onboarding schedule. Access to PRODUCTS.md, ORG.md, README, and CONTRIBUTING files allows the system to extract the tech stack and architecture needed for accurate environment setup and milestone tracking.

How do I track 30/60/90 day onboarding milestones and check-ins for new hires?▼

30/60/90 day onboarding milestones are tracked by creating calendar check-ins, saving a local onboarding document to the docs folder, and logging a summary to memory. This requires write permission to save local docs and integration points for calendar and memory logging.

What's the best way to automate ramp-up schedules for developers joining a specific codebase?▼

The best way to automate developer ramp-up schedules is to use a profile-driven plan that aligns role, level, and product tech stack to produce week-by-week starter tasks and environment checklists. This approach replaces generic onboarding with personalized, product-aware milestones.