vault-skilllisted

## When to invoke this skill This is the **parallel skill twin** of the `vault` MCP server. It manages a local Obsidian knowledge vault at `.claudevault/` in the project root, using plain markdown files linked with `[[wikilinks]]`. The whole system is file-based — no server required, just Read/Write/Edit/Glob/Grep. Invoke it — **proactively, without being asked** — when: - **A decision is made** → create an ADR in `decisions/NNN-title.md` - **A session ends / is wrapped up** → create/append `logs/YYYY-MM-DD.md` - **Project context changes** → update `context.md` - **Reusable knowledge surfaces** → create a note under `knowledge/` - **Session starts** → read `context.md` + the most recent log - **User says** "process raw", "what's in raw?" → classify `raw/` intake - **User asks for a report/briefing/gap-analysis** → write to `outputs/` - **Vault doesn't exist yet** → run Init ## Core principle: maximum linkage Every note links to everything relevant. The test: *if two notes are related in any way, there should be a link between them.* When in doubt, link. Always-apply rules: - Every note links back to `[[context]]` - Every decision links to the session log where it was made - Every decision links to the knowledge notes that informed it - Every session log links to the decisions/knowledge/context changes that session - Every knowledge note links to the decisions and logs that reference it - Related decisions link to each other; superseded decisions cross-link to replaceme