onboard

A continuity ledger maps brownfield codebase architecture and captures essential context for new contributors. It is needed during project discovery or knowledge transfer to reduce ramp-up time and establish a shared understanding of the existing system.

Documenting project discovery is best achieved by generating a structured continuity ledger. This approach guides you through codebase exploration, detects the tech stack interactively, and outputs a Markdown file to preserve handoff context for future developers.

Yes, mapping a codebase for knowledge transfer requires a workspace with a thoughts/ledgers directory. The onboard process outputs the generated continuity ledger directly to this path to ensure consistent documentation storage and retrieval.

Interactive codebase exploration for onboarding works by prompting the developer to understand architecture and detect the tech stack. It systematically guides the user through repository analysis to produce a comprehensive Markdown continuity ledger.

You can prepare for a project handoff without manual documentation by spawning the onboard agent. It automatically analyzes the brownfield codebase and outputs a structured continuity ledger, capturing the necessary context to facilitate a smooth knowledge transfer.