spinup

# /mf:spinup — project memory → session prime Get up to speed on a project without starting any new work. Read persistent memory in priority order, summarise, then **stop** and wait for user direction. ## Important 1. **Spinup is read-only.** Never start work unprompted. Even if the memory says "the next thing to do is X", your job is to _report_ that — not to start doing X. 2. **Read selectively.** Budget 3–6 files for a typical spinup. Reading everything is expensive on context and rarely useful. 3. **Verify what you're about to cite.** Memory is a point-in-time snapshot; file paths, commits, and symbols may be stale. 4. **Don't re-derive settled decisions.** If a feedback memory says "closed as failed", don't re-propose it. ## Instructions ### Step 1: Open `MEMORY.md` directly Auto-memory lives at `~/.claude/projects/<slug>/memory/` where `<slug>` is `$PWD` with every `/` replaced by `-` (deterministic — form the path inline, no shell call needed). On the happy path, go straight to `Read ~/.claude/projects/<slug>/memory/MEMORY.md`. If that read succeeds, you've simultaneously located the dir and loaded the index — skip the rest of this step. Only fall back to diagnostics if the read fails: - **ENOENT on `MEMORY.md`** but the memory dir itself exists → treat as "primed but no memory yet" (step 2 behaviour). - **ENOENT on the memory dir** → the slug convention may differ on this host. Run `ls ~/.claude/projects/ | grep <project_name_fragment>` to find the actual dir;...