memo-writinglisted

# Writing Effective Session Memos ## Context **Date:** !`date +%Y-%m-%d` **Project:** !`basename $(git remote get-url origin 2>/dev/null | sed 's/\.git$//' | xargs basename 2>/dev/null) 2>/dev/null || basename $(pwd)` **Topics available for [[wikilinks]]:** !`ls $(memex path 2>/dev/null)/topics/*.md 2>/dev/null | xargs -I{} basename {} .md | sort | tr '\n' ' ' || echo "(no topics found)"` ## Core Principle **You were there. A subagent reading the transcript later wasn't.** Your memo from full context will always be better than a reconstructed one. Write from experience, not summary. Capture the **journey**, not just the destination. Future-Claude needs to understand: - How things were discovered, not just what was found - What was tried and failed, not just what worked - What surprised you or was unexpectedly hard - Where user and AI disagreed or changed direction ## Memo Format ```markdown --- type: memo title: [Specific, searchable title] project: [project-name] # detected from cwd git root; set explicitly if writing from outside the project date: [ISO date] topics: - topic-name-kebab-case - another-topic manual: true # distinguishes manually-written memos from auto-extracted ones --- # [Title] ## For Future Context [1-2 sentences: the single most important thing for someone continuing this work] ## Summary [2-4 sentences: what was the actual work, not "we discussed X" but "we tried Y, discovered Z"] ## What Happened ### Key Decisions - **[D