Carry project decisions into the next AI work session
At a glance
An Obsidian user keeps raw material, synthesized notes and session state separate so Claude can resume ongoing work with the right context. This workflow is listed under Knowledge Management, Project Planning, AI Memory.
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Create an Obsidian-compatible vault with three areas: unchanged raw captures, a permanent wiki and session-state files. Use Claude in a setup that can read your vault files. 2) Put journals, meeting notes, clips and transcripts in raw; synthesize selected material into wiki notes with Summary, Context and Details sections. 3) Give each wiki note at least two meaningful internal links and connect it to a hub or project note. 4) Maintain a project hub with current state, constraints and decisions. At session start, have Claude read that hub and session-state.md before continuing the work. 5) At session end, update session-state.md with active threads, decisions, unresolved questions and next actions; keep significant-action logs in memory/daily/.
Worth knowing
The author later added vector search for discovery after exceeding 200 notes, while retaining direct file reads for active project context.