memory-manager

To persist project conventions across sessions, use a memory-first protocol that retrieves prior context from markdown notes before executing tasks and writes newly learned architectural decisions back into the memory directory for future reuse.

A memory-first workflow enforces a Research, Response, and Learning cycle for software development, ensuring historical decisions and user preferences are retrieved from existing markdown files before answering and updated conventions are saved afterward.

Retrieve historical project context by running memory search on MEMORY.md and markdown files in the memory directory, then use targeted memory get commands to pull relevant prior notes before writing or answering about past work.

Yes, you can use markdown files to store team knowledge by writing updated architectural decisions and user preferences into the memory directory, allowing autonomous agents to access and apply consistent coding conventions across tasks.

A memory retrieval protocol is not needed for agent execution when a task operates in a completely isolated environment with no historical decisions, or when retrieving prior markdown context adds unnecessary latency to stateless operations.