idea-discovery
The `/idea-discovery` command identifies and ranks three to five candidate directions for next work by systematically gathering ungraduated ideas, open project questions, and orphan research notes from an Obsidian vault, then scoring them by recency, referential pull, and existing momentum. Use this when deciding which captured idea or research thread merits graduation into a full project, ensuring ranking logic is auditable and no candidates are fabricated.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/idea-discovery.md -o ~/.claude/commands/idea-discovery.mdidea-discovery.md
Use the obsidian-second-brain skill. Execute `/idea-discovery`: Answers "what is worth doing next" from material already in the vault. Distinct from `/obsidian-emerge` (which names unstated patterns) and `/obsidian-graduate` (which promotes one chosen idea into a project) - this ranks several candidate directions so you can pick one. 1. Gather candidate signals - list and grep exhaustively (see the anti-fabrication rule): - Ungraduated ideas in `Ideas/` (status `captured` or `exploring`, not yet `graduated`). - Open questions in active project notes (Open Questions sections, unresolved decisions). - Orphan research notes in `Research/` that no project links to. 2. Rank the candidates by a simple, stated heuristic: recency (touched recently), pull (how many notes reference or depend on it), and momentum (does anything already build toward it). State the heuristic in the output so the ranking is auditable. 3. For each of the top 3-5, write: the candidate, why now, the `[[source notes]]`, and the smallest next step that would move it forward. 4. Optionally suggest running `/research [topic]` on a candidate to pull external signal before committing, or `/obsidian-graduate` to promote one into a full project. 5. Save the shortlist to `Ideas/YYYY-MM-DD - discovery.md` (`type: synthesis`, tagged `[thinking, idea-discovery]`) with source links in frontmatter. Do NOT auto-graduate anything - this command only surfaces and ranks. --- **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:** Rank only real candidates found in the vault - never invent an idea, an open question, or a research note to pad the shortlist. Enumerate `Ideas/`, project Open Questions, and orphan research exhaustively rather than sampling. 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
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
Reconcile the vault against your calendar - flag deadlines and commitments implied by notes that are not on the calendar. Flag only, never adds events