onboard-team-to-memory-banks

A memory bank stores shared project knowledge in files like systemPatterns.md and techContext.md to reduce friction during team onboarding. It captures conventions and technical context so teams can reuse knowledge across project handovers and feature ramp-ups.

Start by leading a kickoff workshop to establish shared conventions and create a minimal memory bank within the first week. Generate initial files like systemPatterns.md and techContext.md, then expand documentation as adoption grows.

Yes, phased adoption starts minimal and grows with team needs. This lightweight onboarding approach introduces templates and exercises incrementally to ensure ongoing practice and measurable early wins during feature ramp-ups.

No, you create lightweight documentation during the onboarding process itself. The phased approach uses templates and exercises to build minimal memory banks like systemPatterns.md and techContext.md as part of the initial hands-on adoption.

Team onboarding fails without shared conventions because knowledge capture becomes inconsistent and reusable context is lost. Establishing a plan-prompt-proceed pattern through kickoff workshops aligns the team on practices before creating memory banks.