wisdom

To record project decisions and learnings in an Obsidian vault, append concise entries to dedicated category files like learnings.md and decisions.md. This ensures critical knowledge is preserved beyond session memory and links to detailed notes.

The best way to capture recurring issues in Obsidian for knowledge management is appending short summaries to an issues.md file. This structured method ensures notable issues are preserved with context-aware links for future reference.

You should document architecture decisions in your Obsidian knowledge base whenever a verification resolves, repeated mistakes are identified, or notable learnings occur. Recording these entries immediately ensures critical insights are not lost.

Yes, the wisdom skill requires specific Obsidian vault files to function, specifically learnings.md, decisions.md, and issues.md. Entries are appended directly to these categorized files to maintain a structured knowledge base.

Yes, you can link detailed notes to concise wisdom entries in Obsidian. The skill requires that summaries remain short and apply context-aware linking to related notes so future sessions can reference detailed outcomes.

The recommended format for Obsidian wisdom entries is a concise summary appended to the appropriate category file. Entries must be short, categorically organized, and link to detailed notes when needed to effectively persist notable learnings.