Obsidian panel
/obsidian-panelUse the obsidian-second-brain skill. Execute `/obsidian-panel [decision or question]`:
--- description: Convene a panel representing distinct perspectives on a decision:one independent verdict per perspective, followed by 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"] --- Use the obsidian-second-brainskill . Execute/obsidian-panel [decision or question] : Pressure-tests a decision from several independent angles at once. While/obsidian-challenge red-teams from a single adversarial stance, this gathers a panel of distinct perspectives and has each present its own argument before presenting a synthesis. 1. Determine the decision or question to be addressed by the panel. If none exists, ask what should be presented to the panel. 2. Select the panel: - If the vault contains a “Advisors/ ” folder, review those persona notes and use each as a panelist (each verdict reflects that advisor’s stated perspective and priorities). - Otherwise, use 4 generic perspectives: the skeptic (what could cause this to fail), the user/customer (who benefits or is harmed), the operator (can this actually be implemented and maintained), and the long-term view (what will 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 summary: where the panel agreed, where it disagreed, and a recommended decision along with its main risk. Do not hide the disagreement:the split is the most useful outcome. 5. Save towiki/concepts/YYYY-MM-DD - panel - <slug>.md (type: synthesis , tagged[thinking, panel] ), linking any[[Advisors/...]] notes and[[entities/projects]] that the decision affects. Cross-link from today’s daily note. --- AI-first rule: Every note created or updated by this command MUST followreferences/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 for human reading. Anti-fabrication: If you useAdvisors/ notes, base each verdict on what that note actually says:do not invent an advisor’s position or attribute views to a real person that they have not expressed. Never fabricate a consensus; report the actual split. See the anti-fabrication and search-completeness hard rules atreferences/ai-first-rules.md .