obsidian-board
The obsidian-board command displays and updates kanban boards stored in an Obsidian vault's Boards folder, flagging overdue items with past dates and tracking items stale in their columns for over a week. Use it to review current board state across columns, move completed tasks to a Done column with strikethrough, add new items inferred from conversation context, and keep project status synchronized without manual file editing.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/obsidian-board.md -o ~/.claude/commands/obsidian-board.mdobsidian-board.md
Use the obsidian-second-brain skill. Execute `/obsidian-board $ARGUMENTS`:
The optional argument is a board name. Handle typos and partial matches.
1. Read `_CLAUDE.md` first if it exists in the vault root
2. If a board name is given, search the boards folder for it (fuzzy match), resolved per `references/folder-map.md` (wiki-style `boards/`, Obsidian-style `Boards/`)
3. If no name given, list available boards and ask which one
4. Read and display the current board state: columns, item counts, overdue items (past `@{date}`)
5. Ask if the user wants to make updates - if yes, infer changes from conversation context
6. Move completed items to ✅ Done with strikethrough, add new items in the right column
7. Flag any items that are overdue (past their `@{date}`), and any in-progress items whose `@{date}` is more than a week past. The board format has no per-column timestamps, so date stamps are the only age signal - do not guess column dwell time
---
**AI-first rule:** Board files follow the kanban exception in `references/ai-first-rules.md`: `kanban-plugin` frontmatter, NO `## For future agent` heading (the plugin would render it as a phantom column). Every NON-board note this command creates or updates (task notes, project notes) MUST follow the full rule - preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`), `[[wikilinks]]`, sources verbatim. 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.
**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`.>
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
One calendar command with four modes - agenda (read a snapshot), reconcile (vault vs calendar gaps), meeting (event to note), schedule (task to event)