obsidian-task
The obsidian-task command adds a task to a kanban board within an Obsidian vault, automatically inferring priority level and due date to place it in the correct column ("This Week" or "Backlog"). Use this when you need to quickly capture a task from conversation or arguments and have it organized across linked projects and daily notes while adhering to the vault's AI-first documentation standards and anti-fabrication rules.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/obsidian-task.md -o ~/.claude/commands/obsidian-task.mdobsidian-task.md
Use the obsidian-second-brain skill. Execute `/obsidian-task $ARGUMENTS`: 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Parse the task from the argument, or pull from recent conversation context if no argument given 3. Infer: priority (🔴/🟡/🟢), due date, linked project, linked person 4. Search for the right kanban board - use `_CLAUDE.md` board list or search the boards folder (resolved per `references/folder-map.md`) 5. Add the task card to the correct column (`📋 This Week` or `📥 Backlog` depending on due date) 6. Create a task note in the tasks folder (resolved per `references/folder-map.md` - wiki-style `wiki/tasks/`, Obsidian-style `Tasks/`) if the task is substantial (more than a one-liner) 7. Link the task from the relevant project note and today's daily note --- **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`.
>
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