Vault deep synthesis
/vault-deep-synthesisUse the obsidian-second-brain skill. Execute `/vault-deep-synthesis [topic]`:
--- description: A deep cross-reference of everything the vault knows about a single topic:agreements, contradictions, outdated claims, and coverage gaps. Pure Vault, no network category: thinking triggers_ens: ["synthesize what I know about", "deep synthesis on", "cross-reference my notes on", "what does my Vault say about"] --- 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 entire vault for unnamed patterns without prompting), this takes a topic you specify and reads every note related to it to produce a consolidated view. Pure vault: no network, no API keys. 1. Determine the topic from the argument. If none is provided, ask what to synthesize. 2. Find every note that references the topic:exhaustively search and list 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 corroborated by multiple notes, with [[wikilinks]] to each. - Contradictions:where notes disagree; name both [[notes]] and the specific conflict. Do not resolve them here (/obsidian-reconcile); just bring them to light. - Stale claims:outdated facts that may no longer be true (cite the note and the date). - Coverage gaps:questions raised by the topic 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 the 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-Clauderetrieval:not for human reading. Anti-fabrication: Enumerate the matching notes exhaustively; do not sample:a partial scan reported as complete produces confident but incorrect answers. Never invent a claim, contradiction, or source; if the vault has limited information on the topic, state so. See the strict rules on anti-fabrication and search completeness at references/ai-first-rules.md.