obsidian-graduate — Claude Code command: idea to project
The obsidian-graduate command for Claude Code turns an idea note into a project spec, tasks, kanban cards, and links. It moves a loose concept toward an execution plan.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-graduate does
The command uses the obsidian-second-brain skill. It can find an idea from an argument, tag, or keyword; with no argument, it presents ideas from the last 14 days. It reads the selected note and linked notes, then searches the vault for overlapping projects, mentioned people, earlier decisions, and similar ideas.
It creates a project note with planning status, goals, phased tasks, open questions, and links to related notes. It also adds cards to the relevant kanban board, marks the source idea as graduated, and links the new project from today’s daily note. Folder locations come from references/folder-map.md, while note structure follows references/ai-first-rules.md.
The command reads _CLAUDE.md when that file exists at the vault root. If it cannot read references/ai-first-rules.md, it must report that before writing any notes.
What it helps with
- turn an idea note into a project specification
- search the vault for related projects and past decisions
- split a project into phased tasks with priorities
- add a project and task cards to a kanban board
- connect the source idea with the project and daily note
Example prompts for the agent
- Turn the idea tagged
#ideaabout data imports into a project. - Create a project from the idea note “Personal dashboard” and find related notes.
- Show ideas from the last 14 days and let me choose one for
/obsidian-second-brain:obsidian-graduate.
How to install obsidian-graduate
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-graduate.mdCall it with /obsidian-graduate. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-graduate.mdCall it with /prompts:obsidian-graduate. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-graduate.prompt.mdManually: put the files in place
.gemini/commands/obsidian-graduate.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-graduate
How do I install obsidian-graduate in Claude Code?
In Claude Code, run /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain. The command file is .claude/commands/obsidian-graduate.md.
What does obsidian-graduate do?
It turns an idea in an Obsidian vault into a project note with goals, phased tasks, open questions, board cards, and links to related material.
What happens when references/ai-first-rules.md cannot be read?
The command must report the problem before it writes notes. Every note it creates or updates is expected to follow that file’s rules.
Source text
obsidian-graduate.md · MIT
--- description: Promote an idea fragment into a full project spec with tasks, board entries, and structure category: thinking triggers_en: ["promote idea", "graduate this to project", "make a project from this", "elevate idea"] triggers_de: ["Idee weiterentwickeln", "das zu einem Projekt machen", "aus dieser Idee ein Projekt machen", "Idee zum Projekt ausbauen"] triggers_es: ["promociona esta idea", "convierte esto en proyecto", "haz un proyecto de esto", "eleva esta idea"] triggers_pt: ["promova esta ideia", "transforme isto em projeto", "crie um projeto a partir disto", "eleve esta ideia"] triggers_zh: ["把这个想法变成项目", "将这条灵感升级为项目", "为这个想法建立完整项目", "把它拆成项目和任务"] --- Use the obsidian-second-brain skill. Execute `/obsidian-graduate $ARGUMENTS`: The optional argument is the idea title, tag, or keyword. If not provided, scan recent notes for ideas tagged `#idea` or in the ideas folder (resolved per `references/folder-map.md`) and present them for selection. 1. Read `_CLAUDE.md` first if it exists in the vault root. Resolve the ideas folder and projects folder per `references/folder-map.md` (wiki-style: ideas in `wiki/concepts/`, projects in `wiki/projects/`; Obsidian-style: `Ideas/`, `Projects/`). 2. Find the idea to graduate: - If argument given: search the ideas folder, daily notes, and captures for a matching idea (fuzzy match) - If no argument: list recent ideas (last 14 days) and ask the user to pick one 3. Read the full idea note and any linked notes for context 4. Research the vault for related content: - Existing projects that overlap - People who were mentioned in connection with this idea - Past decisions that relate - Similar ideas that were previously explored (to avoid reinventing) 5. Generate a full project spec: - **Project note** in the projects folder (resolved above) with the full `type: project` schema from `references/ai-first-rules.md` (`type: project`, `date`, `updated`, `status: planning`, `tags: [project]`, `related-people`, `related-projects`, `ai-first: true`) plus `graduated-from: "[[Idea Note]]"` - **Description**: what this project is and why it matters - **Goals**: 3-5 concrete outcomes - **Key tasks**: broken into phases with priorities - **Open questions**: what still needs answering - **Related notes**: links to everything relevant found in step 4 6. Create board entries: - Add a card to the relevant kanban board in `Backlog` or `This Week` - Add individual task cards if multiple phases 7. Update the original idea note: - Add `status: graduated` to frontmatter - Add a link to the new project note 8. Link the new project from today's daily note 9. Report: what was created, what was linked, what needs the user's input The idea doesn't die - it evolves. The original note stays as the origin story, the project note becomes the execution plan. --- **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