conductor-memory

# Conductor Memory Turn a working session into a durable memory pack so the next session starts already knowing the project, the decisions, the working style, and the exact next step. The expensive thing to lose between sessions isn't the code - it's the *reasoning and context*. This skill captures that and lands it where the next session will actually read it: an Obsidian vault and a Claude Code resume pointer. The work splits cleanly: scripts handle the deterministic scaffolding and checks; Claude handles the one thing only Claude can do well - reading the session and synthesizing what mattered. ## When to reach for this Whenever a session produced decisions, state, or context worth carrying forward. the user may say it directly ("build conductor memory", "snapshot this") or it may just be the natural end of a substantial session. When in doubt, offer it. ## What gets produced A single timestamped pack folder containing: - `MEMORY_INDEX.md` - the spine; a "resume here" pointer plus links to everything - `<project>_memory_conversation_summary.md` - decisions, evolution, where we left off - `<project>_memory_artifacts_index.md` - what was created and how it connects - `<project>_memory_communication_style.md` - how to work with the user / persona - `<project>_memory_project_context.md` - profile, stack, goals, success metrics - `<project>_memory_seed_data.json` - the same content, machine-readable - `<project>_memory_personality.yaml` - persona configuration - `<projec...