Seed Vault from Repo

Turn what a repo already knows (code layout, READMEs, docs, ADRs, plans, CI) into linked, sourced vault notes, so research, /write-from-vault, and future sessions can use them. The notes summarize; they don't mirror the code.

Prompt-driven, not a script. Draft first, write only when the user says so, and do one unit per pass.

0. Preconditions

• Read .agent/context/knowledge-vault.md (fallback docs/agents/knowledge-vault.md). If it's missing, stop and tell the user to run /setup-knowledge-vault first. If only knowledge-vault.example.md exists, ask them to copy it and fill in their own path. Never guess a vault path.
• Get git rev-parse HEAD and git status --porcelain. With a dirty tree, ask: seed from HEAD (uncommitted changes ignored) or wait. Every note records source_commit.
• Read the vault's layout and conventions from the Vault Layout section of knowledge-vault.md: index folder (Indexes/ or vault root), flat or substructure, folder names, Title Case, wikilinks, and the project folder from project-context.md. Follow them over the defaults here. If the layout isn't stated, ask the user once and offer to record the answer in knowledge-vault.md. Never assume Indexes/.
• Note titles must be filename-safe: no : / \ ? * < > | ". Use - as the separator (e.g. Plan - Warehouse Migration, Decision Trace - Use DuckDB).
• Argument resync jumps to RESYNC.md.

1. Discover units, then confirm

Find units in this order, and stop at the first source that gives a clear answer: