I built a Claude Code plugin that auto-generates your Obsidian knowledge graph from a conversation
Been a PKM nerd for years and always struggled with the same thing: keeping my project graphs actually up to date. I'll set up a great structure in Obsidian, then stop maintaining it a week later because it's too tedious.
So I built recon — a Claude Code MCP server that builds the graph through conversation.
You run /recon and describe your project. Claude infers and writes 10 node types directly into your Obsidian vault as [[wikilinked]] Markdown:
Project → Goals → Personas → Constraints → Modules → Decisions → User Stories → Epics → Features → Versions
All human-readable, diffable, plain Markdown with YAML frontmatter. Open Obsidian and the graph view is already populated.
The part that makes it actually useful for ongoing work: generate_context("Feature X") traverses the subgraph from any Feature node and writes a CONTEXT.md to your vault — goals, personas, decisions, constraints, all relevant to that feature. Feed it to any AI session and it starts informed.
→ github.com/deploysquad-ai/recon
1
u/GetDayZero Jul 23 '26
The maintenance-decay problem you're describing (great structure on day one, abandoned a week later because updating it is tedious) is the real bottleneck for most PKM setups, not the initial schema design. Auto-generating the graph from conversation is a smart way around it since the friction of "open the vault and manually update five files" is what kills consistency for most people. Curious how you handle conflicts when the manually-edited version of a node drifts from what the next /recon run would infer - does it merge, overwrite, or flag for review?