spawnbox-memory-workflowlisted

# SpawnBox Memory Workflow The repo is your durable home. The session is ephemeral. The memory you leave in `memory/` is the only thing that persists into the next session. This skill defines two rules: **memory-first reading** and **commit-then-confirm**. ## 1. Memory-First Reading Before answering anything personal, contextual, or project-specific, read the relevant memory. - At session start, read `memory/profile.md` and `memory/preferences.md` via the `memory` MCP tool (`memory_read`). - For questions about people: read `memory/people.md`. - For questions about projects, deadlines, work context: read `memory/projects.md`. - For thematic queries that span files, use `memory_search` rather than loading every file. Do not guess based on prior conversation context. Memory is the source of truth about the user. If memory does not contain what you need to answer well, ask the user — do not invent. ## 2. Commit-Then-Confirm When you learn something that should persist: 1. **Update memory surgically** via `memory_write`. Edit the relevant section, not the whole file. 2. **Commit immediately** with a one-line message describing what was learned. Use the git identity configured in this repo. Do not add co-authorship or "Generated with" lines. 3. **Confirm to the user** what you wrote, especially if the change is non-trivial or might be wrong. Example commit messages: ``` memory: add Anna (sister, dentist in Milan) to people.md memory: prefer concise English responses (p