vault-suggest-for-plan

Finding vault citations for plan tasks is automated by reading a Markdown plan file, extracting each Task description and Goal sentence, and batch-querying the vault to map tasks to existing knowledge slugs or flag gaps.

Mapping plan tasks to vault knowledge is handled by preparing targeted queries per task and batch-searching the vault, returning a structured report that identifies matching knowledge slugs or flags missing areas requiring stubs.

Generating a research log from a Markdown plan file is supported by extracting goals and task descriptions, querying the vault, and producing a ready-to-paste Research-log entry that accelerates enrichment with vetted citations.

Identifying vault gaps when planning documentation is achieved by scanning plan Markdown, running deep searches per task, and emitting a structured report that explicitly flags gaps requiring vault-gap stubs.

Specifying a plan path is optional when requesting vault notes for a plan; the skill triggers on specific commands and invocation phrases, supporting an optional plan path argument to target the correct Markdown file.

When a vault search finds no matching citations for a task, the structured report flags the specific task area as a gap, indicating that a vault-gap stub must be created to cover the missing knowledge.