AI-Enhanced Onboarding

The traditional onboarding curve is shaped by a single bottleneck: a senior engineer has 90 minutes a day to answer questions, and the new hire has a week's worth of questions queued by lunch on day one. Every conversation that gets deferred is a half-day of stalled progress.

An agent that's read your CLAUDE.md, your README, your architecture docs, and your last 200 commits doesn't replace the senior engineer — but it absorbs 70% of the questions that don't actually need them.

The shape of the workflow

1. Step 1Day 0Repo + docs handoff
2. Step 2Day 1Agent setup + first PR
3. Step 3Week 1Pairing on real work
4. Step 4Week 2Solo PRs land
5. Step 5Day 30Reverse-onboard a teammate

Two parallel tracks, one human one agent. The new hire moves between them based on the question type, not based on the day of the week.

What the agent gets prepped on (Day 0)

A senior engineer spends ~30 minutes preparing this. Done once per project, reused per hire.

• CLAUDE.md at the root, full and current. This is the single highest-leverage artifact. See the Claude Code Operational Patterns playbook.
• An ONBOARDING.md with the things you'd say in the kickoff conversation: who owns what, where the non-obvious documentation lives, the three modules new hires get lost in and why.
• The last 30 days of commits are implicitly available via git log.
• Architecture docs if they exist, linked from CLAUDE.md.

The test: a new hire asks "how does authentication work in this codebase?" and the agent gives the right answer with file paths in under 30 seconds. If it doesn't, the prep was incomplete.

What the human does (still)

Things the agent can't substitute for, ranked by leverage:

1. The why. Why we picked this stack, why we made these tradeoffs, what we tried that didn't work. Goes in CLAUDE.md but lands harder when said in a person.
2. The org map. Who to ask about what. Who's grumpy, who's slow, who'll say yes if you bring coffee. Goes in nobody's docs; transmitted in person.
3. The first real PR. Pair on it. The agent helps with the code; the senior engineer helps with the review etiquette, the commit-message conventions, the "this is how we do it here" moments.
4. The 1:1 at the end of week 2. "What's still confusing? What did the agent get wrong?" Both answers improve CLAUDE.md for the next hire.

What this changes about hiring

Two things, both real:

• Junior engineers ramp materially faster. The questions they're embarrassed to ask, they ask the agent first. The questions worth the senior engineer's time are different than they used to be.
• The bar for "good docs" goes up. A codebase with a thin CLAUDE.md onboards slowly even with the agent, because the agent has nothing to ground its answers in. The investment moves from "I'll explain it the next time someone asks" to "I'll write it down once."

The second-order effect: teams that adopt this start writing markedly better docs because the docs are now read by the agent on every new hire. The audience changed; the standard followed.

Anti-patterns to avoid

• "The agent replaces the buddy." It doesn't. It absorbs questions; the buddy provides the org context.
• "Ship the new hire a list of prompts to use." Ineffective. They need the workflow, not the magic words. They learn the prompts by using them.
• "Treat the agent's wrong answers as the new hire's problem." They're the docs' problem. Catch them in the day-30 retro and fix CLAUDE.md.

The honest version

This doesn't make onboarding easy. It makes it less blocked. A new hire still has to read code, learn the domain, build the mental model. The agent removes the asymmetric cost where one person's curiosity stalls another person's day. That's worth a lot.