Skip to main content
command CX Codex

obsidian-decide — Claude Code command: what it does, how to install

obsidian-decide — a Claude Code command that extracts decisions from a conversation and files them in Obsidian, as dated lines or, with --formal, as a full ADR.

MIT ★ 5,412 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain
Open on GitHub

What obsidian-decide does

obsidian-decide pulls decisions out of the current conversation and writes them into your Obsidian vault. In the default mode each decision becomes a dated line under ## Key Decisions in the matching project note, and a summary goes into today's daily note. A decision that touches several projects is logged in each one. Pass a topic as an argument to narrow the search.

Add --formal, or start the argument with adr, and it writes a full Architecture Decision Record instead: the decision, what triggered it, 2-3 options weighed, the reasoning, consequences and related notes. The project note gets a link to the record, index.md is updated, and the action is appended to the operation log. A folder reorganization or a stack choice fits this mode.

The command runs through the obsidian-second-brain skill, so install the plugin first. To dig up decisions that exist only in commits, formal mode calls scripts/mine_commit_decisions.py with uv run, which means uv must be installed. If a _CLAUDE.md sits in the vault root, it is read before anything else.

What it helps with

  • log decisions from a long discussion into the project note with a date
  • record one decision across several projects at once
  • write up a stack choice as an ADR with options and consequences
  • find decisions in git history that nobody documented
  • leave a link that explains why the folders are structured the way they are

Example prompts for the agent

  • Run /obsidian-decide and log the decisions from this conversation into the project notes
  • Use /obsidian-decide --formal for the folder restructuring we just agreed on
  • Go through the git history and write up unrecorded decisions with /obsidian-decide --formal

How to install obsidian-decide

1Plugin marketplace

/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain

2Manually: put the files in place

.claude/commands/obsidian-decide.md

Call it with /obsidian-decide. For all projects use ~/.claude/commands/

Questions about obsidian-decide

How do I install obsidian-decide in Claude Code?

Run /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain.

What does obsidian-decide do?

It finds decisions made during a conversation and files them in Obsidian. A plain call adds dated lines to ## Key Decisions in project notes and a summary to the daily note.

How is the default mode different from --formal?

The default mode leaves short entries in project notes. --formal creates a separate ADR with context, options, rationale and consequences, links it from the project note and updates index.md.

Source text

obsidian-decide.md · MIT
---
description: Record decisions - lightweight by default (logged to project notes), or a full ADR record with --formal
category: thinking
trigger-mode: proactive
triggers_en: ["extract decisions", "log decisions", "what did we decide", "log this decision", "ADR", "record decision", "decision record"]
triggers_de: ["Entscheidungen herausarbeiten", "Entscheidungen festhalten", "was haben wir entschieden", "diese Entscheidung protokollieren", "ADR", "Entscheidung dokumentieren", "Entscheidungsprotokoll"]
triggers_es: ["saca las decisiones de esta conversación", "registra las decisiones", "¿qué decidimos?", "anota esta decisión", "ADR", "acta de decisión formal"]
triggers_pt: ["extraia decisões", "registre decisões", "o que decidimos", "registre esta decisão", "adr", "registrar decisão", "registro de decisão"]
triggers_zh: ["记录这个决定", "我们刚才决定了什么", "把这些决策整理出来", "生成决策记录", "写一份 ADR"]
---

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

Two depths, one command. The optional argument narrows focus to a topic. Add `--formal` (or lead with `adr`) to write a full Architecture Decision Record instead of a one-line log entry.

- **Default (lightweight):** capture decisions from the conversation as dated one-liners in the relevant project notes. Use for the steady stream of choices made while working.
- **`--formal` (ADR):** write one structured decision record with context, options, rationale, and consequences. Use for a structural or directional decision worth a full writeup (a folder reorg, a convention adopted, an idea graduated, a stack choice).

1. Read `_CLAUDE.md` first if it exists in the vault root.

### Lightweight mode (default)

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

### Formal mode (`--formal`)

2. Identify the structural decision - from the argument or recent conversation (a project graduated, a folder reorganized, a convention adopted, a concept promoted to hub). To surface decisions already made in code but never recorded, run `uv run --directory "SKILL_ROOT" scripts/mine_commit_decisions.py --repo <project> --json` (the skill root was given at session start as **Skill root**; substitute it for `SKILL_ROOT`) - it scans git history for decision-shaped commits ("switch to", "replace", "adopt", "rename", "migrate") and returns ADR candidates.
3. Create a decision record in the decisions folder resolved per `references/folder-map.md` (wiki-style `wiki/decisions/YYYY-MM-DD - Title.md`, Obsidian-style `Knowledge/ADR-YYYY-MM-DD - Title.md`), with frontmatter `date`, `type: adr`, `status: accepted`, `tags: [adr, decision]`, `ai-first: true`. Structure:
   - **Decision** - one-line summary of what was decided.
   - **Context** - what prompted it (the problem or trigger).
   - **Options Considered** - 2-3 alternatives evaluated.
   - **Rationale** - why this option over the others.
   - **Consequences** - what changes as a result (notes created, moved, restructured).
   - **Related** - links to affected project notes, people, ideas.
4. Update the relevant project note's `## Key Decisions` section with a link to the record, and update `index.md`.
5. Append to the operation log (`Logs/YYYY-MM-DD.md` if it exists, else `log.md`) and link from today's daily note.

Decision records keep the vault from becoming a black box: when a future session asks "why is it structured this way?", the ADR answers. Other commands may offer to call the formal mode - when `/obsidian-graduate` promotes an idea, when `/obsidian-health` recommends a structural fix, or when folders are reorganized - offer, do not force.

---

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

© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set51

The whole set →
research Research a topic and get a sourced dossier. With free sources, Claude Code turns the returned results into a note. CX Codex +1 ★ 5,412repo stars crew crew synchronizes a work logbook across Claude Code, Codex, Cursor, and Grok Bot via a local folder. Lets each agent see what others did, what patterns emerged, and decide next steps from a shared record. CX Codex +1 ★ 5,412repo stars obsidian-export obsidian-export generates a structured snapshot of an Obsidian vault as flat JSON, a single Markdown index, or an Open Knowledge Format bundle. CX Codex +1 ★ 5,412repo stars obsidian-world obsidian-world is a Claude Code command that loads context from an Obsidian vault in stages. It runs on requests to catch up or check current priorities. CX Codex +1 ★ 5,412repo stars obsidian-save obsidian-save extracts decisions, tasks, ideas, and contacts from a Claude Code session directly into an Obsidian vault. Useful for archiving working context without manual note-taking. CX Codex +1 ★ 5,412repo stars obsidian-learn The obsidian-learn command reviews lessons in an Obsidian vault, marks stale or replaced findings, and surfaces repeated patterns for _CLAUDE.md. CX Codex +1 ★ 5,412repo stars obsidian-catchup obsidian-catchup — a command to review everything you dumped into the Telegram journal bot on the go—voice, text, images, PDFs, links—and integrate it into your Obsidian vault with Claude Code when you're back at the laptop. CX Codex +1 ★ 5,412repo stars obsidian-retrieval-eval obsidian-retrieval-eval evaluates Obsidian vault search quality using recall@k and MRR metrics. It tests search ranking against natural-language questions before changing indexing. CX Codex +1 ★ 5,412repo stars

Project sponsors

Companies that keep this analytics open