Your first week on a system
Work through the part of the system you will change with your onboarding buddy. Start a conversation in Investigations with an accessible codebase and branch. Your administrator can help if the agent cannot read the repository you need.
- Ask: “Where is webhook delivery implemented on this branch? Trace a delivery from the entry point through the queue, retry decision, and tests. Cite the files in each step.”
- Ask Driver to explain one handoff at a time and open the cited code. With prepared Advanced context, ask it to use the Atlas to identify the owning subsystems and relationships to trace the connected files. Basic source search can locate the entry points and follow direct references.
- Ask about unfamiliar terms and ownership evidence. Have your buddy explain conventions or operational practices that are absent from the code and supplied documents.
- Supply a small proposed change, such as adding a retryable status. Ask: “Which callers and tests should I inspect before changing this condition? Separate direct references from assumptions about other services.”
- Ask for a compact onboarding note with the flow, entry-point files, test commands found in the repository, codebase branch, and open questions. Review it with your buddy and copy it into your onboarding notes or team documentation.
If you prefer a coding assistant, connect it through Driver MCP and ask it to read the same branch. With Advanced context, the assistant can use get_atlas_index, get_atlas_detail, and get_related for the map and connections. Your team runs tests and local development commands in its own environment.