Migrate Memory

Intent

Help an already-developed project acquire a readable, trustworthy memory foundation. The emphasis is understanding the project and initializing useful StrictDoc documentation, not moving old files or converting every artifact.

Use judgment about investigation depth, document structure, storage overlap, and which questions need the user's input. There is no fixed inventory, mandatory classification report, or approval ceremony for every initialization.

Understand the project as it exists

• Look across project instructions, README, main modules, entry points, configuration, existing docs, and relevant development history. Follow the evidence far enough to understand purpose, architecture, conventions, current state, and unfinished work.
• Existing Magic Context memories and claude-mem observations can recover decisions or experiences not visible in code. Their absence does not prevent initializing StrictDoc.
• Read the useful sources in context rather than assuming particular note names, plan directories, or an older development methodology. Generated output and exhaustive transcripts rarely need the same attention as key code and decisions.
• Separate intended policy, observed implementation, past experience, and unresolved questions. Newer evidence can reveal change without automatically settling what the current rule ought to be.

Build a useful memory foundation

The companion save-mem skill describes memory maintenance and StrictDoc mechanics. Its assets/docs-skeleton/ is a starting point, located through the skill registry or the sibling ../save-mem/ directory, not a fixed home-directory path.