memory-initlisted

Run once per project. Gives `checkpoint` somewhere to read and write. If you use Claude Code, this is not its built-in `/init`. That one writes a `CLAUDE.md` describing your codebase, and it is worth running. This one creates the files that carry state between sessions, and it leaves any existing instruction file standing. ## The three files All under `memory/`. Each has one job, and the split is what keeps the first one short enough to be read every session. | File | Job | Write style | |---|---|---| | `PROJECT.md` | What this project is, right now | Edited in place. Stays under one screen | | `DECISIONS.md` | Why it is that way | Append only, newest at top | | `SESSIONS.md` | What happened, and when | Append only, newest at top | ## Steps 1. **Survey first.** Read the instruction file your agent reads, if the project has one: `AGENTS.md`, `CLAUDE.md`, or your agent's equivalent. List `memory/`. Done when you can name which of the four target files already exist. 2. **Back up anything that exists.** Copy each existing target to `<filename>.bak` beside it. A file with no `.bak` does not get written to. Done when every file you intend to modify has a backup. 3. **Learn the project before writing about it.** Read the README, the build and test config, the entry point, and the directory layout. Run the test command if there is one, and record whether it passed. Done when you can state in your own words what the project does, how it is run, and how it is