onboarding-buddy git:20261104.4860813A

Immutable. This exact content never changes and is served at /api/v1/blob/98cdaeeb32c09abe.

---
name: onboarding-buddy
description: Builds a dated first-fortnight plan for a new joiner from the team's own documents, meetings and systems, naming who they meet and what they read on which day. Use when the user asks to plan an onboarding, prepare for a new starter, build a first-week plan, or says someone is joining the team.
---

# Onboarding Buddy

Turns "they start Monday" into a dated plan built from what the team actually has.

## Inputs
- **Enterprise Search** for the team's existing material: handbooks, architecture notes, runbooks
- **Calendar Management** for who is available in the first fortnight
- `references/config.md` for the role templates and the standing first-week items

## Procedure
1. **Establish** the start date, the role and the team. Missing any of these, ask once and stop.
2. **Find the real material.** Search for what this team has written: onboarding notes, decision
   records, runbooks, recent all-hands. Record what exists and, importantly, what does not.
3. **Find the people** the role should meet, evidenced by who owns the systems and documents the
   role will touch. Not an org chart walk.
4. **Build the plan day by day** across ten working days, each day carrying at most one meeting
   and one reading item. A plan with six meetings on day one is a plan nobody follows.
5. **Propose calendar holds.** Do not create them.
6. **List the gaps.** If there is no runbook for a system the role owns, that is the most useful
   output in the whole plan.

## Output
Day-by-day table:

| Day | Date | Meet | Why them | Read | Source |

Then: material that exists, material that is missing, and the proposed holds for the user to
approve.

## Definition of done
Ten working days planned, every reading item linked, every person justified by what they own, and
the missing material named.

**A short plan with real links beats a full one with placeholders.** If the team has written
little, say so: the gap list becomes the onboarding plan's most valuable section.

## When there is no data
- No team material found: say so clearly and build the plan from people only, marking every
  reading slot as MATERIAL NEEDED.
- Start date unknown: do not assume next Monday.

## Boundaries
- **Never create calendar events or send invitations.** Propose holds for approval.
- Never include anything about the joiner's compensation, background or personal details.
- Never surface documents the joiner will not have permission to open once they start: note them
  as access needed instead.
- Draft only.

## Self-check
- Is every person justified by ownership, not hierarchy?
- Is every reading item a real link?
- Did I name what is missing rather than papering over it?