agent-memory-disciplinelisted

# Agent memory discipline ## Overview Connecting a memory tool does not make an agent use it: tools register, the session runs, and nothing gets recalled or saved. This skill supplies the missing part, standing rules for when to read memory and when to write it. The problem it solves is specific. An agent with memory available still repeats settled questions, reverts corrected habits, and loses decisions between sessions, because nothing tells it when recall and save are due. The rules below make both moments explicit. ## Prerequisites - A memory tool the agent can call. Any backend works, and the rules are identical for each: - **Files.** A `memory/` folder of Markdown notes, one fact per file. No dependencies, fully greppable, versionable in git. - **A local MCP memory server.** Keeps everything on the local machine; several open-source options exist. - **A hosted memory service over MCP.** Adds portability across tools and machines at the cost of the data living elsewhere. - Authentication is whatever the chosen backend requires: none for a local folder, the server's own configuration for a local MCP server, an API key or OAuth sign-in for a hosted service. This skill never handles credentials itself and never writes them into memory. ## Instructions ### Step 1: Recall before acting Read memory **before** doing any of these, not after: - starting work on a project touched before - choosing a library, pattern, or tool - writing tests, commits, or documentatio