obsidian-project — Claude Code command: projects, install
Creates or updates an Obsidian project note, then links it to a board and the daily note. It fits vaults that track projects through structured notes.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-project does
The command searches the vault for an exact or approximate project name, including likely typos. When it finds a match, it shows the result and asks for confirmation before editing it. When no match is found, it creates Project Name.md in the folder resolved through references/folder-map.md, fills in details from the conversation, and places a card in 📥 Backlog or 🔨 In Progress.
The note follows the project schema from references/ai-first-rules.md, with project status, dates, tags, related people and projects, and ai-first: true where applicable. The command also links the project from today’s daily note. It reads _CLAUDE.md at the vault root before making changes when that file exists.
The rules require inline source URLs, [[wikilinks]] for referenced entities, and explicit handling of unknown facts instead of invented details. If references/ai-first-rules.md cannot be read, the command must report that before writing the note.
What it helps with
- create a structured project note
- find a project despite a typo
- update project goals and status
- put a project on the kanban board
- link the project to today’s note
Example prompts for the agent
- Run
/obsidian-project Website launchand create the project from our conversation. - Use
/obsidian-project database migrationto search for close matches and ask before editing one. - Update
/obsidian-project Internal portalwith the latest details and link it from today’s note.
How to install obsidian-project
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/obsidian-project.mdCall it with /obsidian-project. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-project.mdCall it with /prompts:obsidian-project. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-project.prompt.mdManually: put the files in place
.gemini/commands/obsidian-project.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-project
How do I install obsidian-project in Claude Code?
Add the marketplace with /plugin marketplace add eugeniughelbur/obsidian-second-brain, then install the plugin with /plugin install obsidian-second-brain@obsidian-second-brain. The command file is .claude/commands/obsidian-project.md.
What does obsidian-project do?
It creates or updates a project note, adds a card to 📥 Backlog or 🔨 In Progress, and links the project from the daily note for today.
How does it handle an approximate project name?
It searches for a close match, shows what it found, and asks for confirmation. It should not silently create a note under a misspelled name.
Source text
obsidian-project.md · MIT
--- description: Create or update a project note - adds to board and daily note automatically category: vault triggers_en: ["new project", "create project note", "project setup", "start a project"] triggers_de: ["neues Projekt", "Projektnotiz erstellen", "Projekt einrichten", "ein Projekt starten"] triggers_es: ["nuevo proyecto", "crea una nota de proyecto", "configura el proyecto", "arranca un proyecto", "crea un proyecto nuevo"] triggers_pt: ["novo projeto", "crie uma nota de projeto", "configuração de projeto", "inicie um projeto"] triggers_zh: ["创建一个新项目", "新建项目笔记", "开始这个项目", "为项目建立基本结构"] --- 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 `Project Name.md` in the projects folder (resolved per `references/folder-map.md` - wiki-style `wiki/projects/`, Obsidian-style `Projects/`) with the full `type: project` schema from `references/ai-first-rules.md` (`type: project`, `date`, `updated`, `status: active`, `tags: [project]`, `related-people`, `related-projects`, optional `job`, `ai-first: true`) 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 agent` 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. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent 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`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain