establish-memory-bank

Project knowledge continuity across context resets is maintained by establishing a structured memory bank of six core markdown files that document project state, decisions, and progress for immediate recovery. This system survives context window clearing by storing critical information externally.

A memory bank documentation system for onboarding is a six-file structure containing project brief, product context, system patterns, tech context, active context, and progress. It enables new team members to review defined reading order documents and resume work with minimal questions.

To set up a memory bank, create a memory-bank/ directory at your project root and initialize six core markdown files: projectbrief.md, productContext.md, systemPatterns.md, techContext.md, activeContext.md, and progress.md, then record initial state and decisions.

The best way to document project decisions for team transitions is recording them with explicit rationale within a structured memory bank. This ensures incoming personnel understand the reasoning behind architectural choices and project direction without relying on verbal handover.

You need to update memory bank files after each work session by modifying activeContext.md and progress.md. Additionally, defined update triggers and stewardship self-reflection prompts dictate when to refresh the other four stable core documents to keep information evergreen.

This memory bank system works for projects with frequent personnel changes by providing an evergreen knowledge base with cross-reference guidelines and a defined reading order. New contributors can immediately continue work by accessing the structured documentation instead of querying departing team members.