git-pr-workflows-onboard

Generates structured onboarding plans with 30/60/90-day milestones for new team members.

2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/monang404/lunawave --skill git-pr-workflows-onboard-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr-workflows-onboard
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/git-pr-workflows-onboard
Command: npx skills add https://github.com/monang404/lunawave --skill git-pr-workflows-onboard-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New hires often face disorganized onboarding that delays productivity and weakens team integration. This Skill produces structured, role-specific onboarding plans covering pre-arrival preparation through the first 90 days. ## Core Features & Use Cases - Customized Onboarding Plans: Generates plans based on role, seniority, location (remote/hybrid/on-site), and team structure. - Milestone Tracking: Defines 30/60/90-day checkpoints with measurable criteria like first PR merged, feature ownership, and on-call readiness. - Buddy System & Integration: Provides buddy responsibility matrices, team immersion activities, and feedback loops for continuous improvement. - Use Case: A manager onboarding a remote senior engineer can request an accelerated plan covering architecture deep-dives, stakeholder introductions, and 30-day deliverables. ## Quick Start Ask the assistant to create a 90-day onboarding plan for a remote software engineer starting next Monday, including pre-boarding setup and milestone checkpoints.

Frequently Asked Questions about git-pr-workflows-onboard

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

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

Provide the role, seniority, start date, location, and team context, and the Skill generates a phased plan. Day 30 focuses on foundational training and first commits, Day 60 on feature ownership, and Day 90 on independent delivery and mentoring.

How to onboard a remote software engineer effectively?▼

Remote onboarding plans cover home office stipends, equipment shipping, virtual team introductions, timezone-friendly schedules, and async communication norms. Daily coffee chats and recorded sessions help distributed hires integrate without in-person contact.

What should a buddy system include during onboarding?▼

A buddy system assigns a dedicated peer for 30 days with daily check-ins in week one, tapering to weekly syncs. The Skill provides a responsibility matrix defining frequency, activities, and time commitments across the first 12 weeks.

Does this onboarding approach work for senior or lead engineers?▼

Yes, it includes an accelerated track for senior hires emphasizing architecture deep-dives, postmortem reviews, technical debt assessment, and stakeholder relationship building. Thirty-day deliverables include a technical assessment document and process improvement plan.

What are the limitations of a template-based onboarding plan?▼

Template plans require customization for role, seniority, and team context to remain effective. They provide structure and checklists but cannot replace manager judgment, and success still depends on consistent feedback collection and iteration.