Employee Onboarding Plan Builder

What it takes in

The inputs you provide on each run, validated before anything executes.

3 tasks, run in order.

Each task passes its result to the next. Here's what each does and what it produces.

1. 01
   Build the 30-60-90 day plan. From {{roleTitle}} and {{teamContext}}, design a staged onboarding plan covering the first 30, 60, and 90 days. For each stage define: the goals to achieve, the learning milestones (what the new hire should understand about the product, team, and processes), the relationship-building targets (who to meet, in what order, and why each relationship matters for this role), and how success is measured at the end of the stage. If {{toolsSystems}} is provided, weave tool proficiency milestones into the appropriate stages. If {{startDate}} is provided, anchor each stage to approximate calendar dates. Do not invent people, tools, or policies not present in the inputs. Present this as a readable staged plan, never JSON.

   Expected output

   A readable 30-60-90 day plan with no JSON and no code blocks, with one clearly headed section per stage (First 30 Days, Days 31 to 60, Days 61 to 90). Each stage shows: Goals (bullets), Learning Milestones (bullets), Relationship Targets (who to meet and why), and Success Measures (how the manager and new hire will know the stage is complete). If a start date was provided, each stage heading includes its approximate date range.
2. 02
   Lay out week-one logistics. Using the plan from Task 1 plus {{teamContext}} and {{toolsSystems}}, build the practical first-week runbook: a day-by-day schedule for the new hire's first five working days (mixing orientation, setup, learning, and early meetings), an access and equipment checklist covering every tool or system mentioned in {{toolsSystems}} plus standard items like email, calendar, and hardware, and a buddy and manager check-in cadence for the first month (who checks in, how often, and what each check-in should cover). If {{startDate}} is provided, label the days with actual dates. Present readably, never JSON.

   Expected output

   A readable week-one logistics section with no JSON and no code blocks containing: Day-by-Day Schedule (Day 1 through Day 5, each with a short list of activities and meetings), Access & Equipment Checklist (checkbox-style bullets grouped into before-day-one and week-one items), and Check-in Cadence (buddy and manager check-ins with frequency and the focus of each).
3. 03
   Draft the ready-to-send messages. Using {{roleTitle}}, {{teamContext}}, and the plan from Tasks 1 and 2, write two drafts: a welcome email to the new hire (warm and practical, covering what to expect in week one, key logistics from Task 2, and who their main contacts are) and a team intro announcement (a short message introducing the new hire to the team, their role, what they will own, and encouraging the team to say hello). Use square-bracket placeholders only for details not present in the inputs, such as [New Hire Name]. Present as readable, ready-to-send copy, never JSON.

   Expected output

   Two clearly separated, ready-to-send drafts with no JSON and no code blocks: Welcome Email (with a Subject line and body) and Team Intro Announcement (a short message suitable for email or chat). Any missing details appear as square-bracket placeholders so the manager can fill them in quickly.