manager-agent-start

To preserve coding context across sessions, initialize a file-based project memory to save repository state, decisions, and history into a dedicated directory. This lightweight snapshot loads automatically on subsequent visits.

The best way to initialize project memory is to trigger a workflow that interviews you about the project, explores the repository, and creates a memory directory containing six tracking files for state, history, and risks.

A file-based project memory workflow operates by creating a directory with six files to track memory, project state, todos, bugs, decisions, and risks. It loads a project snapshot for context before enforcing a deterministic workflow.

You do not need to manually manage project memory files after initialization. The workflow coordinates with a paired update skill to sync changes back to memory and produce a task-focused summary after work is complete.

Yes, you can use project memory snapshots for large repository collaboration. The system uses lightweight layered loading to speed initial responses and adds the memory directory to gitignore to prevent conflicts.