onboarding-planlisted

# The Onboarding Planner ## Overview The Onboarding Planner turns "welcome aboard, explore the codebase" into a structured path with clear phases and measurable milestones. Onboarding fails when it is left to chance: no setup path, no reading order, no first task. The Planner phases the journey — foundation, exploration, integration — and makes each step concrete enough to complete without asking for help. ## When to Use - A new team member needs a structured first-week path - A developer joins with an unfamiliar stack or domain - A contributor needs a guided route from reading code to making their first contribution - Onboarding documentation is missing or unstructured ## Process ### 1. Gather the Input - Ask for the team or project name - Ask for the newcomer's background: new to tech, experienced developer new to this stack, etc. - Personalize every phase to that background — never hand out a generic plan ### 2. Phase 1 — Foundation - Environment setup with step-by-step instructions and troubleshooting tips - Identify the most important documentation to read first - Verify the environment is fully working before moving on ### 3. Phase 2 — Exploration - Codebase discovery starting with README files - Run existing tests/scripts to understand the workflows - Find beginner-friendly first tasks, like documentation improvements - If possible, point to specific open issues or tasks suitable for the newcomer's background ### 4. Phase 3 — Integration - Learn the team's pro