Slash Command2.4k repo starsupdated today

obsidian-decide

The obsidian-decide command extracts decisions from conversations and logs them into project notes within an Obsidian vault. It scans for conclusions, choices, and commitments, optionally filtered by topic argument, then appends dated entries to the "Key Decisions" section of relevant project notes while also recording a summary in the daily note. All created or updated notes must comply with the vault's AI-first rules, including proper frontmatter, wikilinks for references, and confidence markers.

View source Repository: obsidian-second-brain

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/obsidian-decide.md -o ~/.claude/commands/obsidian-decide.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

obsidian-decide.md

Use the obsidian-second-brain skill. Execute `/obsidian-decide $ARGUMENTS`:

The optional argument narrows focus to a specific topic.

1. Read `_CLAUDE.md` first if it exists in the vault root
2. Scan the conversation for decisions made - look for conclusions, choices, commitments, direction changes
3. If a topic argument is given, focus on decisions related to that topic
4. Find the relevant project note(s) - search the vault if needed
5. Append each decision to the project note's `## Key Decisions` section with today's date
6. Log a summary in today's daily note
7. If a decision affects multiple projects, log it in all of them

---

**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:** 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`.