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

> Role title, department, and any role-specific requirements (tools, certifications, access needs)

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 existing profile on the new hire)

3. Review the loaded context on this new hire.

Gather checklist requirements:

ROLE INFO
- Job title and department
- Required tools and systems access
- Compliance or certification requirements
- Team-specific training needs

LOGISTICS
- Equipment needs (laptop, phone, etc.)
- Office/desk requirements
- Badge/building access needs


4. Create a checklist organized by phase using the categories from the guide:
- Pre-boarding (before day 1): equipment, accounts, workspace, buddy, scheduling
- Day 1: paperwork, benefits, access, equipment, introductions
- Week 1: training, stakeholder meetings, system verification
- Days 1-30: compliance training, team meetings, first project, 30-day check-in
- Days 31-90: 60-day check-in, performance review, 90-day review, goal setting

Use checkbox format (□) for each item. Include specific items relevant to the role.


5. Add role-specific items based on department:
- Engineering: codebase access, dev environment, code review setup
- Sales: CRM access, territory assignment, shadowing schedule
- Customer Success: support tools, customer list, product deep-dive
- Marketing: brand guidelines, content tools, campaign access
- Finance: financial systems, approval authorities, reporting access

Note which items are owned by HR vs. Manager vs. IT.


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