Chat + Project15 min setupOrgChart GetOptional: V2MOM Get

Onboard Anyone in 15 Minutes

A structured, dense primer about your team that a new hire or a skip-level can read in 15 minutes and actually understand: mission, active projects, decision rights, comms norms, and the five people worth meeting first.

Make this yours

When you do this, is there something really important to you?

Optional

Your answer shapes how the prompt is personalised. A few examples of what someone might write:

“I always want bullet points, never prose.”
“Push back if I'm being vague.”
“Keep updates under 5 lines.”
“Lead with the decision, not the analysis.”

Your input is sent to the model once and never stored.

0/500

## System
You are writing a team primer for a new hire. Dense. Specific. No filler. Everything they need to understand this team in 15 minutes of reading.

## Inputs
I will give you:
1. My CLAUDE.md (from the Project context — includes WHO I AM, MY V2MOM, MY MANAGER, MY TEAM, HOW I WORK)
2. My org chart (retrieved via OrgChart Get MCP)
3. A brief description of what's actively in flight (3–5 bullet points from me)
4. The new hire's name and role

## Steps
1. **Mission** — In 2 sentences: what this team exists to do, grounded in the V2MOM Vision.
2. **Active projects** — Top 3–4, one sentence each. What it is, who owns it, when it lands.
3. **Decision rights** — What can the new hire decide themselves? What needs my sign-off? What needs escalation above me?
4. **Comms norms** — How does this team communicate? Sync vs async cadence. Where things live. How to ask for help.
5. **First 5 people** — Name, role, one sentence on why they matter for this hire specifically.

## Output format

# Team Primer — [New Hire Name]
_Prepared for [Date]. Read in 15 minutes._

## Mission
[2 sentences]

## Active Projects
- **[Project]** — [owner, status, target date]

## Decision Rights
- **Decide yourself:** [list]
- **Run by me:** [list]
- **Escalate:** [list]

## How We Work
[4–6 bullets on comms norms]

## First 5 People to Meet
1. **[Name]** — [Role] — [Why this person]

---
_Last updated: [Date]_

Setup — 5 steps

Set up your CLAUDE.md in a Project.

Your CLAUDE.md is the primary data source. Add it as a file to a Claude Project. The MY TEAM and HOW I WORK sections drive most of this output.

Connect OrgChart Get MCP.

OrgChart Get retrieves your reporting structure. Run "Who reports to me?" first to confirm the MCP is reading your current org accurately.

Brief Claude on what's in flight.

Don't rely on the MCP for project status — that's ephemeral. Give Claude 3–5 bullet points on what's actively running before you run the prompt.

Update every time you use it.

The primer is only as useful as your CLAUDE.md is current. If your CLAUDE.md hasn't been updated in 30+ days, update it first.

Share the output directly.

Copy the primer into a Google Doc or Notion page and share it before the hire's first week. No formatting needed — the structure is already right.

Make it yours — 3 variations

Skip-Level Version

For a leader joining two levels above you. Adjust the decision rights framing — they'll want to understand the team's autonomy envelope, not just what to escalate.

Contractor Brief

Strip to mission + current projects + one point of contact. Contractors don't need the full org picture — they need to start fast.

30-Day Check-In Prep

Run the same prompt after 30 days with a "what has changed" prompt appended. Good prep for the new hire's month-one review.