create-command
CommandCreate a new obsidian-second-brain command via interview - zero markdown editing required
Promote an idea fragment into a full project spec with tasks, board entries, and structure
> /plugin marketplace add eugeniughelbur/obsidian-second-brain> /plugin install obsidian-second-brain@obsidian-second-brain
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:
3. Read the full idea note and any linked notes for context 4. Research the vault for related content:
5. Generate a full project spec:
6. Create board entries:
7. Update the original idea 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`.
<!-- author-credit -->
---
From [obsidian-second-brain](https://github.com/eugeniughelbur/obsidian-second-brain), created by Eugeniu Ghelbur (AI Automation Engineer, AI Tooling Engineer, AI Educator). Questions or consulting: [LinkedIn](https://www.linkedin.com/in/eugeniu-ghelbur/) or [e.ghelbur@gmail.com](mailto:e.ghelbur@gmail.com). More: [The AI Operator](https://theaioperator.io/?utm_source=github&utm_medium=file-credit) | [X](https://x.com/eugeniu_ghelbur) | [GitHub](https://github.com/eugeniughelbur). MIT license.
Persistent memory for Claude Code, Codex and 6 other AI agents, stored as plain markdown in your Obsidian vault. New: Crew, one shared logbook so Claude Code, Codex, Cursor and Grok Bot know what each other did. 48 commands: semantic search, self-rewriting notes, key-less research, scheduled agents.
Create a new obsidian-second-brain command via interview - zero markdown editing required
Share a plain-folder logbook across Claude Code, Codex, Cursor, and Grok Bot
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is…
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep…
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions.…
Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass
Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…