Onboarding Snapshot

New developers joining a team routinely lose hours, sometimes days, just reading through an unfamiliar codebase before they can make their first meaningful contribution. Existing documentation is often outdated, missing, or too high-level to be actionable, leaving new devs to reverse-engineer the architecture on their own. Onboarding Snapshot solves this by using IBM Bob as an onboarding assistant that takes a raw repository and turns it into two concrete outputs: a plain-language architecture explanation covering what the codebase does, how a request or piece of data flows through it, and what each major file or module is responsible for; and two beginner-friendly starter tasks that are real, scoped pieces of work a new developer can complete on day one, instead of just reading documentation passively. Target users are new engineers joining an existing codebase, engineering managers who want faster ramp-up for hires, and open-source maintainers who want to lower the barrier to first-time contributors. To demonstrate this, we ran Bob IDE's agent mode against a real, production codebase, Express.js, a well-known Node.js web framework, chosen for its real-world complexity and recognizability. Bob explored the repository structure end-to-end using its file-listing, file-reading, and symbol-overview tools across the lib/, test/, and root config files. It synthesized this into a structured, file-by-file architecture breakdown, including a request-flow diagram showing how a request moves from the HTTP layer through application.js, the router, middleware, and finally the response helpers. It then reasoned about the existing test suite's patterns to propose two starter tasks scoped appropriately for a beginner, each pointing to exact files. What makes this creative and unique is that it doesn't just summarize a README, it actively reads and reasons over the real source and test code the way a thoughtful senior engineer would when mentoring a new hire, then converts that understanding into an actionable first task rather than a passive explanation. The impact is significant: it cuts the "read the whole codebase before touching anything" phase from hours to minutes, gives new developers a guided first contribution instead of an overwhelming blank slate, and scales to any repository Bob can index, not just Express.