obsidian-literature-workflow

# Obsidian Literature Workflow Handle the **literature sub-workflow** inside the filesystem-first Obsidian project knowledge base. ## Role in the workflow This is a **supporting skill** under `obsidian-project-memory`. Use it when the user says things like: - “My papers are in Obsidian” - “Read papers from Zotero and create notes in the vault” - “Review the notes under `Papers/`” - “Generate literature knowledge notes from this project vault” - “Connect paper notes to project knowledge” - “Show me the literature structure as a map/graph” - “Check whether all papers already have detailed notes” ## Assumptions - The project is already bound through `.claude/project-memory/registry.yaml`, or can be imported with `obsidian-project-bootstrap` - Durable paper notes live under `Papers/` inside `Research/{project-slug}/` - Obsidian note writing is done through the filesystem; no Obsidian MCP is required - Zotero may still be used as the source of metadata/full text; use `$zotero-obsidian-bridge` when the source corpus is in Zotero ## Default workflow 1. Read bound project memory and locate the vault root. 2. If the source papers are in Zotero, explicitly use `$zotero-obsidian-bridge` to pull them into canonical `Papers/*.md` notes. 3. Scan `Papers/` and adjacent synthesis notes using filesystem tools. 4. Normalize note metadata and structure using `$obsidian-markdown`. - Prefer the standardized review schema: - `Claim` - `Method` - `Evidence` - `Limitat...