THE ONBOARDING DOC BUILDER

Hiring your first VA / contractor / part-timer? They need to know what you know — without 47 calls. This skill builds the onboarding doc: business overview, your standards, tools, who's who, recurring tasks, escalations. One read. They're ready.

THE PROBLEM

Hiring help is the unlock that lets you scale past your own hours. The block is onboarding. You don't write the doc because you don't have time, then you spend 4x more time answering the new person's questions.

10 minutes upfront with this skill = 4 hours saved in their first month.

THE SKILL

You give Claude:

Your business (what it does, who it serves)
The role they're hired for
Tools they'll use
Recurring tasks they'll own
Your standards (turnaround time, communication style, quality bar)

Claude returns a complete onboarding doc.

INSTALL

Standard.

THE FULL SKILL FILE

---
name: onboarding-doc-builder
description: Generates a complete onboarding doc for VAs, contractors, or part-time hires. Includes business overview, role definition, tools list, recurring tasks, communication standards, escalation paths, and the first-30-days plan.
when_to_use: User says "onboarding doc," "hiring a VA," "contractor handoff," or describes wanting to bring someone in to help with their work.
---

# The Onboarding Doc Builder

You build onboarding docs that prevent follow-up questions. Specific. Standards-aware.

## Inputs
1. **Business** — what it does, who it serves
2. **Role** — what they're hired for
3. **Tools** — they'll use
4. **Recurring tasks** — they'll own
5. **Your standards** — turnaround, communication, quality

## Output

ONBOARDING DOC — [Role title] For: [New hire's name or "you"] From: [User] Last updated: [Date]

═══════════════════════════════════════ ABOUT THE BUSINESS ═══════════════════════════════════════ [3 sentences on what we do, who we serve, our edge]

═══════════════════════════════════════ YOUR ROLE ═══════════════════════════════════════ [2 sentences — the title and outcome you own]

WHAT YOU OWN:

[Specific responsibility 1]
[Specific responsibility 2]
[Specific responsibility 3]

WHAT YOU DON'T OWN (so we're clear):

[Thing they might assume but isn't theirs]
[Thing the user keeps]

═══════════════════════════════════════ TOOLS YOU'LL USE ═══════════════════════════════════════

[Tool 1] — for [what]
[Tool 2] — for [what]
[Tool 3] — for [what]

Access setup:

[Steps for them to get logins / invitations]

═══════════════════════════════════════ RECURRING TASKS (with SOPs) ═══════════════════════════════════════

[Task 1] — Frequency: [X] · SOP: [link if exists, otherwise build with Day 71]
[Task 2] — Frequency: [X] · SOP: [link]
[Task 3] — Frequency: [X] · SOP: [link]

═══════════════════════════════════════ WHO'S WHO ═══════════════════════════════════════

[User] — the buck stops here
[Existing team members if any]
[Key clients / suppliers / collaborators they'll interact with]

═══════════════════════════════════════ COMMUNICATION STANDARDS ═══════════════════════════════════════

Turnaround time: [normal / urgent / emergency]
Channels: [Slack / email / Loom video / what for what]
Don't ping me about: [things they should solve themselves]
DO ping me about: [things you want to know]
Office hours / async expectations: [when they should expect responses]

═══════════════════════════════════════ ESCALATION ═══════════════════════════════════════

If [situation], do [action]
If [bigger situation], message me + don't proceed
If [emergency], call (not message)

═══════════════════════════════════════ QUALITY BAR ═══════════════════════════════════════ "Good enough" looks like: [specific examples] "Not good enough" looks like: [specific examples]

═══════════════════════════════════════ FIRST 30 DAYS ═══════════════════════════════════════

WEEK 1: Read all this. Set up tools. Shadow me on [task] once. Ask anything. WEEK 2: Run [Task 1] with my review. WEEK 3: Own [Task 1] independently. Run [Task 2] with review. WEEK 4: Own [Task 1] + [Task 2]. Suggest improvements based on what you've seen.

═══════════════════════════════════════ QUESTIONS BEFORE YOU START? ═══════════════════════════════════════ Reply by [date] with anything unclear. Otherwise we're good to go.


## What NOT to do

- Don't include things the user hasn't done yet (don't promise SOPs that don't exist)
- Don't write more than 2 pages (longer = unread)
- Don't include passwords / credentials in the doc
- Don't recommend hiring for tasks the user can't yet describe themselves

## Delivery

End with: *"Send the doc + their first 30 days. Hold a 15-min call after they've read it. Don't repeat what's in the doc."*

SAFETY CHECK

Same as Day 1.

WHAT'S NEXT

Day 92 of 100. Pair with Day 71 — SOP Builder (referenced in this doc) and Day 45 — The Delegator.