vault-deep-synthesis
`/vault-deep-synthesis` exhaustively cross-references every note in your vault touching a named topic, surfacing agreements, contradictions, stale claims, and coverage gaps into a single synthesis document. Use it when you need a comprehensive, vault-only view of what you already know about a subject without external research, and when you want to identify internal conflicts or gaps before deeper investigation.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/vault-deep-synthesis.md -o ~/.claude/commands/vault-deep-synthesis.mdvault-deep-synthesis.md
Use the obsidian-second-brain skill. Execute `/vault-deep-synthesis [topic]`: A focused, topic-driven cross-reference of the existing vault. Unlike `/obsidian-synthesize` (which scans the whole vault for unnamed patterns unprompted), this takes a topic you name and reads every note touching it to produce one consolidated view. Pure vault: no network, no API keys. 1. Resolve the topic from the argument. If none, ask what to synthesize. 2. Find every note that references the topic - grep and list exhaustively across `wiki/`, `Research/`, `Knowledge/`, `Ideas/`, and any project folders (do not sample; see the anti-fabrication rule). Match by every plausible name, alias, and folder. 3. Read the matching notes and cross-reference them into: - **What the vault agrees on** - claims multiple notes corroborate, with `[[wikilinks]]` to each. - **Contradictions** - where notes disagree; name both `[[notes]]` and the specific conflict. Do not resolve them here (that is `/obsidian-reconcile`); just surface them. - **Stale claims** - dated facts that may no longer hold (cite the note and the date). - **Coverage gaps** - questions the topic raises that the vault does not answer. 4. Write the synthesis to `wiki/concepts/YYYY-MM-DD - synthesis - <topic-slug>.md` (`type: synthesis`, tagged `[research, thinking, vault-deep-synthesis]`), listing the source notes it read in frontmatter. 5. Do NOT modify the source notes - this command only reads and synthesizes. Append a one-line entry to the operation log. --- **AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future Claude` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. The vault is for future-Claude retrieval - not human reading. **Anti-fabrication:** Enumerate the matching notes exhaustively, do not sample - a partial scan reported as complete produces confident wrong answers. Never invent a claim, contradiction, or source; if the vault is thin on the topic, say so. See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
>
Create a new obsidian-second-brain command via interview - zero markdown editing required
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is worth working on next
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep (which is open-web via Perplexity).
Generate a decision record when the vault structure changes - the vault knows why it knows what it does
Read Google Calendar and write an AI-first snapshot to the vault - today, week, next week, or a custom range
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits
Show or update a kanban board - flags overdue items, updates from conversation