/obsidian-task
Add a task to the right kanban board with inferred priority and due date
> /plugin marketplace add eugeniughelbur/obsidian-second-brain > /plugin install obsidian-second-brain@obsidian-second-brain
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/obsidian-task
Context preview
What this command does when you run it.
Add a task to the right kanban board with inferred priority and due date
Command definition
obsidian-task.mddescription: Add a task to the right kanban board with inferred priority and due date
category: vault
trigger-mode: proactive
triggers_en: ["add task", "new todo", "track this", "remind me"]
triggers_es: ["añade una tarea", "nuevo pendiente", "haz seguimiento de esto", "recuérdamelo"]
triggers_pt: ["adicione uma tarefa", "novo a fazer", "acompanhe isto", "me lembre disto"]
triggers_zh: ["添加一个任务", "记个待办", "跟踪这件事", "提醒我处理这个", "把这件事放到看板"]
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 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. 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-Claude 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`.
Read more
description: Add a task to the right kanban board with inferred priority and due date category: vault trigger-mode: proactive triggers_en: ["add task", "new todo", "track this", "remind me"] triggers_es: ["añade una tarea", "nuevo pendiente", "haz seguimiento de esto", "recuérdamelo"] triggers_pt: ["adicione uma tarefa", "novo a fazer", "acompanhe isto", "me lembre disto"] triggers_zh: ["添加一个任务", "记个待办", "跟踪这件事", "提醒我处理这个", "把这件事放到看板"]
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 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. 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-Claude 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`.
Persistent memory for Claude Code and 6 other CLI agents, stored as plain markdown in your Obsidian vault. Stop re-explaining your projects, decisions and people every session. 45 commands: hybrid semantic search, self-rewriting notes, key-less web research, and scheduled agents that maintain the vault while you sleep.
Repo: eugeniughelbur/obsidian-second-brain
Other commands on obsidian-second-brain.
- /create-command
Create a new obsidian-second-brain command via interview - zero markdown editing required
Open command - /idea-discovery
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is worth working on next
Open command - /notebooklm
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).
Open command - /obsidian-architect
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
Open command - /obsidian-board-hygiene
Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass
Open command - /obsidian-board
Show or update a kanban board - flags overdue items, updates from conversation
Open command

