obsidian-project
The `/obsidian-project` command creates or updates project notes in an Obsidian vault, automatically linking them to kanban boards and daily notes. Use it to capture new projects or modify existing ones from conversation context, with fuzzy matching to catch typos and mandatory confirmation before any action, ensuring AI-first formatting conventions and exhaustive search to prevent false note creation.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/obsidian-project.md -o ~/.claude/commands/obsidian-project.mdobsidian-project.md
Use the obsidian-second-brain skill. Execute `/obsidian-project $ARGUMENTS`: The argument is a project name. Handle typos and partial matches. 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Search the vault for an existing project matching the name (fuzzy - handle typos) 3. If found: show what was found, confirm with user, then update with new info from conversation 4. If not found: create `Projects/Project Name.md` with full frontmatter schema (`date`, `tags: [project]`, `status: active`, `job`) 5. Fill in everything inferable from the conversation: description, goals, key people, current status 6. Add a card to the relevant kanban board in the `📥 Backlog` or `🔨 In Progress` column 7. Link from today's daily note If the name has a typo or is approximate, search the vault, show what was found, and confirm before proceeding. Never silently create a note with a misspelled name. --- **AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future Claude` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. The vault is for future-Claude retrieval - not human reading. **Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
>
Create a new obsidian-second-brain command via interview - zero markdown editing required
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is worth working on next
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep (which is open-web via Perplexity).
Generate a decision record when the vault structure changes - the vault knows why it knows what it does
Read Google Calendar and write an AI-first snapshot to the vault - today, week, next week, or a custom range
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits
Show or update a kanban board - flags overdue items, updates from conversation