task icon Task

Create First Week Schedule

Generate a detailed day-by-day schedule for a new hire's first week

Requirements
Role title, manager name, team members, and key stakeholders to meet
3

Review the loaded context on the new hire and their team members.

Gather first week planning details:

PEOPLE

  • Manager name
  • Team members (names and roles)
  • Buddy (or who should be buddy)
  • Key stakeholders to meet

LOGISTICS

  • Start time on day 1
  • Office location or remote setup
  • Equipment status
  • Access/accounts to provision

TRAINING

  • Required compliance training
  • Product/company overview sessions
  • Team-specific onboarding sessions
4

Create a day-by-day first week schedule:

MONDAY (Day 1)
Morning:

  • Welcome and introductions
  • Workspace/equipment setup
  • IT/access provisioning
  • HR paperwork and benefits overview

Afternoon:

  • Meet the team (informal)
  • 1:1 with manager: expectations overview
  • End-of-day check-in

TUESDAY-THURSDAY (Days 2-4)

  • Daily: Buddy check-in (15 min)
  • Mix of:
    • Training sessions
    • Stakeholder introductions
    • Reading/context time
    • System/tool walkthroughs
    • First small task or shadow assignment

FRIDAY (Day 5)

  • Buddy reflection conversation
  • Manager 1:1: first week wrap-up
  • Questions and clarification time
  • Preview of week 2
5

Include practical details:

  • Suggested meeting durations (30 min for intros, 60 min for training)
  • Buffer time for questions and processing
  • Lunch plans (team lunch day 1?)
  • End times (don't overload day 1)

Flag what needs to be scheduled vs. self-directed.

                    To run this task you must have the following required information:

> Role title, manager name, team members, and key stakeholders to meet

If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.

---

You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple CONSECUTIVE read steps in a row, read them all at once (in parallel). Otherwise, do not read a file until you reach that step.

Add all steps to your todo list now and begin executing.

## Steps

1. [Read Onboarding Guide]: Read the documentation in: `skills/sauna/[skill_id]/references/hr.onboarding.guide.md`

2. [Read People Directory]: Discover relevant information in the user's filesystem at `documents/knowledge/people/*.md`. (Check for profiles of new hire and team members they'll meet)

3. Review the loaded context on the new hire and their team members.

Gather first week planning details:

PEOPLE
- Manager name
- Team members (names and roles)
- Buddy (or who should be buddy)
- Key stakeholders to meet

LOGISTICS
- Start time on day 1
- Office location or remote setup
- Equipment status
- Access/accounts to provision

TRAINING
- Required compliance training
- Product/company overview sessions
- Team-specific onboarding sessions


4. Create a day-by-day first week schedule:

MONDAY (Day 1)
Morning:
- Welcome and introductions
- Workspace/equipment setup
- IT/access provisioning
- HR paperwork and benefits overview

Afternoon:
- Meet the team (informal)
- 1:1 with manager: expectations overview
- End-of-day check-in

TUESDAY-THURSDAY (Days 2-4)
- Daily: Buddy check-in (15 min)
- Mix of:
  - Training sessions
  - Stakeholder introductions
  - Reading/context time
  - System/tool walkthroughs
  - First small task or shadow assignment

FRIDAY (Day 5)
- Buddy reflection conversation
- Manager 1:1: first week wrap-up
- Questions and clarification time
- Preview of week 2


5. Include practical details:
- Suggested meeting durations (30 min for intros, 60 min for training)
- Buffer time for questions and processing
- Lunch plans (team lunch day 1?)
- End times (don't overload day 1)

Flag what needs to be scheduled vs. self-directed.


6. [Gather Requirements for Resolve Person Entity] The next step has the following requirements: "Person information to resolve: name (required), email (if known), service source (gmail/slack/calendar/etc), relationship context, and any additional identifiers (Slack handle, LinkedIn, etc.)". Search the user's data for this information or ask them directly if needed. Do not proceed until you have this information.

7. [Execute Resolve Person Entity Task]: Spawn a subagent and provide it with the requirements gathered above and instructions to read `skills/sauna/[skill_id]/references/recipes/context.entity.resolve_person.md` for its task list