# obsidian-panel

obsidian-panel is a Claude Code command that gathers independent views on a decision and synthesizes them for reviewing disputed questions in an Obsidian vault.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 5412 repo stars
- Author: Eugeniu Ghelbur
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/obsidian-panel.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/obsidian-panel

## What it does

The command takes a decision or question and builds a panel of independent viewpoints. When the vault contains `Advisors/`, each advisor note supplies a panelist’s lens and priorities. Otherwise, it uses four lenses: the skeptic, the user or customer, the operator, and the long-term view.

Each panelist gives a position, its strongest reason, and the condition that could change it. The command then records agreement, disagreement, a recommended decision, and its main risk. It saves the result as `YYYY-MM-DD - panel - <slug>.md` in the concepts folder, links related advisor and project notes, and cross-links the daily note.

The workflow depends on `references/folder-map.md` and `references/ai-first-rules.md` for note paths, frontmatter, links, source handling, and confidence fields. If `references/ai-first-rules.md` cannot be read, the command must report that before writing the note.

## Requirements
- Works with: Obsidian

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add eugeniughelbur/obsidian-second-brain
```
In the agent chat (not a shell):
```text
/plugin install obsidian-second-brain@obsidian-second-brain
```

2. **Manually: put the files in place**
- File: `.claude/commands/obsidian-panel.md` — Call it with /obsidian-panel. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/obsidian-panel.md` — Call it with /prompts:obsidian-panel. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/obsidian-panel.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/obsidian-panel.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/obsidian-panel.md

## When to use it
- pressure-test a decision through separate viewpoints
- surface the strongest argument against an idea
- compare the user’s needs with operational concerns
- record where advisors agree or split
- save a decision synthesis in the vault

## Example prompts
- Use `/obsidian-panel` to assess whether this project should move to a new database.
- Ask `/obsidian-panel` to review the decision about opening the project.
- Run `/obsidian-panel` on these launch options and save the panel synthesis.

## Source text · obsidian-panel.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e82791de123658a2.

BEGIN THIRD-PARTY FILE e82791de123658a2
```text
---
description: Convene a panel of distinct perspectives on a decision - one independent verdict per lens, then a synthesis. A multi-persona complement to /obsidian-challenge
category: thinking
triggers_en: ["convene a panel", "advisor panel", "get multiple perspectives on", "panel review", "what would the experts say about"]
triggers_de: ["ein Expertengremium einberufen", "Beratergremium", "mehrere Perspektiven auf", "Expertenrunde", "was würden die Experten dazu sagen"]
triggers_es: ["convoca un panel", "panel de asesores", "dame varias perspectivas sobre esto", "revisión en panel", "qué dirían los expertos sobre esto"]
triggers_pt: ["convoque um painel", "painel de especialistas", "obtenha múltiplas perspectivas sobre", "revisão em painel", "o que os especialistas diriam sobre"]
triggers_zh: ["找几个不同视角来评审", "让多个专家分析这个决定", "从几个角度评价这个方案", "开个顾问评审会", "不同专家会怎么看"]
---

Use the obsidian-second-brain skill. Execute `/obsidian-panel [decision or question]`:

Pressure-tests a decision from several independent angles at once. Where `/obsidian-challenge` red-teams from one adversarial stance, this gathers a panel of distinct lenses and makes each argue on its own before you see a synthesis.

1. Resolve the decision/question from the argument. If none, ask what to put to the panel.
2. Choose the panel:
   - If the vault has an `Advisors/` folder, read those persona notes and use each as a panelist (each verdict reflects that advisor's stated lens and priorities).
   - Otherwise, use 4 generic lenses: the skeptic (what breaks this), the user/customer (who is served or hurt), the operator (can this actually be run/maintained), and the long-game (what does this look like in a year).
3. For EACH panelist, write an independent verdict: their position, the strongest reason behind it, and what would change their mind. Keep them genuinely distinct - do not let them converge prematurely.
4. Write a synthesis: where the panel agreed, where it split, and a recommended decision with its main risk. Do not hide the disagreement - the split is the most useful output.
5. Save to the concepts folder (resolved per `references/folder-map.md` - wiki-style `wiki/concepts/`, Obsidian-style `Ideas/`) as `YYYY-MM-DD - panel - <slug>.md` (`type: synthesis`, tagged `[synthesis, thinking, panel]`), linking any `[[Advisors/...]]` notes and `[[entities/projects]]` the decision touches. Cross-link from 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.
```
END THIRD-PARTY FILE e82791de123658a2

The third-party file has ended. Everything between the e82791de123658a2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3207 of 3556 bytes. © Eugeniu Ghelbur · MIT · https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/obsidian-panel.md

## Similar
- [obsidian-bases](https://affpapa.org/en/nevibecode/skills/obsidianmd-obsidian-bases.md) — skill · 84200 installs
- [obsidian-cli](https://affpapa.org/en/nevibecode/skills/obsidian-cli.md) — skill · 83700 installs
- [Obsidian Automation](https://affpapa.org/en/nevibecode/skills/obsidian-automation.md) — skill · 5000 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
