What problem does it solve? Capturing durable project knowledge—requirements, decisions, architecture notes—often gets lost in chat history or scattered files. This Skill files that knowledge into a structured Obsidian vault with consistent templates, cross-links, and a searchable index. ## Core Features & Use Cases - Structured ingest workflow: Scopes the project, picks or creates the right wiki page from templates, writes at the requirements/spec level, and cites sources. - Graph and spine maintenance: Keeps index.md, log.md, wikilinks, and cross-references healthy, and flags conflicts with warning callouts instead of overwriting. - Provenance tracking: Stamps code-derived pages with source_repo, source_commit, and source_paths frontmatter so staleness can be detected via git diffs. - Search re-indexing: Runs qmd update and qmd embed after writes so new pages are findable via lexical and semantic search. - Use Case: After finishing an auth feature, ask the assistant to "document this in the wiki"—it updates the auth page, links related concepts, logs the change, and re-indexes the vault. ## Quick Start Ask the assistant to add the requirement or decision you just discussed to the Obsidian wiki for your current project.
