obsidian-second-brain

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

Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass

Multi-turn Socratic brainstorm - one question per turn until the idea converges, then a design note with named alternatives and one recommendation

One calendar command with four modes - agenda (read a snapshot), reconcile (vault vs calendar gaps), meeting (event to note), schedule (task to event)

Quick idea capture - zero friction, saves to your ideas folder and mentions in daily note

Review and process everything captured on the go from the Telegram journal bot - voice, text, images, PDFs, links - waiting in the catchup queue. You pull it when you are back at the laptop; nothing is processed autonomously.

Red-team your current idea against your own vault history - finds contradictions, past failures, and flawed assumptions

Bridge two unrelated domains using your vault's link graph - forces creative friction to spark new ideas

Create or update today's daily note - pulls calendar events, overdue tasks, and conversation context

Record decisions - lightweight by default (logged to project notes), or a full ADR record with --formal

Condense a long note or source into key claims, each tagged with provenance back to the exact source block it came from

Surface unnamed patterns from your recent notes - recurring themes, hidden connections, and conclusions you haven't explicitly stated

Export a clean structured snapshot of the vault that any agent or tool can consume - flat JSON, markdown index, or an OKF (Open Knowledge Format) bundle

Smart vault search - returns results with context, not just filenames

Promote an idea fragment into a full project spec with tasks, board entries, and structure

Run a vault health check - grouped by severity, detects contradictions, concept gaps, stale claims, and structural issues

Ingest a source into the vault - the vault rewrites itself around new knowledge. Every ingest updates entities, rewrites stale claims, synthesizes new concepts, and resolves contradictions.

Scan your vault and generate a _CLAUDE.md operating manual, index.md catalog, and log.md pointer