From obsidian-kb
Initializes project knowledge base: scaffolds Obsidian vault if missing (with confirmation), populates with curated docs via parallel subagents, and audits stale documentation.
How this command is triggered — by the user, by Claude, or both
Slash command
/obsidian-kb:kb-init [vault name] - optional vault name hint if auto-detection picks the wrong vaultThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /kb-init
Trigger the **kb-init** skill. Read the instructions from `${CLAUDE_PLUGIN_ROOT}/skills/kb-init/SKILL.md` in this plugin and follow them exactly.
This is the **full initialization** flow: if the project has no vault yet, it runs `kb-scaffold` first (with user confirmation), then proceeds to analyze the codebase via parallel subagents and write curated documentation notes - including a Documentation Audit that flags stale claims in existing project markdown.
**Always ask for user confirmation before proceeding** - this uses meaningful compute and takes a few minutes.
User argu...Trigger the kb-init skill. Read the instructions from ${CLAUDE_PLUGIN_ROOT}/skills/kb-init/SKILL.md in this plugin and follow them exactly.
This is the full initialization flow: if the project has no vault yet, it runs kb-scaffold first (with user confirmation), then proceeds to analyze the codebase via parallel subagents and write curated documentation notes - including a Documentation Audit that flags stale claims in existing project markdown.
Always ask for user confirmation before proceeding - this uses meaningful compute and takes a few minutes.
User arguments: $ARGUMENTS
npx claudepluginhub waelmas/codeplow --plugin obsidian-kb/kb-initInitializes or rebuilds a project-scoped Obsidian knowledge base vault under Research/{project-slug}/, scaffolding core Markdown files and folders like Sources, Knowledge, and Experiments.