eg-memsync

# /eg-memsync (`/egmem`) — reconcile agent memory ↔ project docs Agent memory and project docs drift apart in **both directions**, and each direction is a real failure mode. Memory absorbs corrections faster than docs do — so a doc keeps stating a policy that a dated memory has since revised, sometimes while citing that very memory file by name. And docs (plus the repo itself) move on while memory keeps stale state — a memory still "waiting" on a gate that was resolved dozens of releases ago, or an index whose one-line summaries no longer match the files they index. Either way the next session inherits a contradiction and has to guess. This skill is the periodic true-up. ## 0. Locate the two corpora - **Memory** — the per-project agent memory store: on Claude Code, the project's auto-memory directory (`memory/*.md` plus its index file); otherwise the workspace's `memory/feedback_*.md` convention or the harness equivalent. **No memory store → nothing to reconcile.** Say so and stop — do not invent one. - **Docs** — the project's governance surfaces: `AGENTS.md` (the SSoT), `.agent/rules.md` (operational detail), and the per-tool bridge files (`CLAUDE.md` and friends). A project not on the AGENTS.md pattern routes to `/eg-migration` first; a project with no seed at all routes to `/eg-bootstrap`. Read both corpora fully before judging anything — drift detection on a partial read produces false confidence. ## 1. Detect drift — five kinds Sweep every memory file against ever...