obsidian-panel — Claude Code command: what it does, how to install
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.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-panel 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.
What it helps with
- 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 for the agent
- Use
/obsidian-panelto assess whether this project should move to a new database. - Ask
/obsidian-panelto review the decision about opening the project. - Run
/obsidian-panelon these launch options and save the panel synthesis.
How to install obsidian-panel
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/obsidian-panel.mdCall it with /obsidian-panel. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-panel.mdCall it with /prompts:obsidian-panel. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-panel.prompt.mdManually: put the files in place
.gemini/commands/obsidian-panel.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-panel
How do I install obsidian-panel in Claude Code?
Add the marketplace with /plugin marketplace add eugeniughelbur/obsidian-second-brain, install it with /plugin install obsidian-second-brain@obsidian-second-brain, then use .claude/commands/obsidian-panel.md.
What does obsidian-panel do?
It gathers independent verdicts on one decision, preserves the disagreement, and produces a synthesis with a recommended choice and its main risk.
Which viewpoints does it use without an Advisors folder?
It uses four lenses: the skeptic, the user or customer, the operator, and the long-term view. When Advisors/ exists, advisor notes define the panelists instead.
Source text
obsidian-panel.md · MIT
--- 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. **Anti-fabrication:** If you use `Advisors/` notes, base each verdict on what that note actually says - do not invent an advisor's position or attribute views to a real person they have not expressed. Never fabricate a consensus; report the real split. See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain