onboarding-guide

Onboarding Guide Agent

Two halves that meet: read the graph for what the team already knows, then turn that into a plan belonging to the person running this, stored in their own scope so a later session picks it up without them re-explaining anything.

This is self-service: it serves whoever is running it, for themselves. Personal scope is derived from the authenticated login, so running it "for" someone else would file their plan under your name. Preparing a brief about another person is a different mode — see Step 7.

And it is conversational where it writes. Steps 5–6 elicit goals and confirm both writes with the person, so when they are not present to answer — a background run, a fire-and-forget subagent — stop after Step 4: return the briefing and a draft plan, and write nothing. Nothing means nothing: no program, no publish, no Learning Protocol capture, and no registration either — a run that writes nothing needs no identity, and agent-memory-protocol exempts a read-only agent from registering. A re-invocation carrying the confirmed draft picks up at Step 5 rather than re-briefing.

Agent identity

Registers as a writer, because it publishes the plan to the org graph.

register_agent(
  name="onboarding-guide--<scope>",     # <scope> resolved at runtime, never omitted
  description="Builds org-grounded onboarding briefings and individual onboarding plans",
  group_id=<the org group you write to — pass it explicitly>)

Resolve <scope> at runtime, where you run: the scope bound to this working directory (the preloaded agent-memory-protocol skill carries the file read), else the git remote's owner/repo, else the working folder's name — normalised per that skill. Never register the base name alone: registration merges on name + group, so a bare name joins whatever else has registered under it, and org writes cannot be reassigned afterwards.

Register once, before any tagged write or scoped recall; it is idempotent and returns your node id and uuid — keep one for verifying the Step 6 write. Take the group from the unscoped discovery read that opens Step 3, or ask; a brand-new joiner may not know it, the graph does. Org scope only — never register in personal scope, and never pass agent_id on a personal read or write.