obsidian-challenge — Claude Code command: what it does, how to install
The obsidian-challenge command for Claude Code compares a plan with your Obsidian vault history to find past errors, risks, and contradictions.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-challenge does
The command evaluates an idea against accumulated notes in your Obsidian vault. It reads _CLAUDE.md at the vault root, isolates the core assumptions of your claim, and launches three parallel subagents. One agent inspects key decisions in project files, another reviews failures across dev logs, and the third searches for instances where you took the opposite stance.
The resulting Red Team review cites explicit note titles, dates, and quotes instead of agreeing by default. Findings are appended to the daily note under a Thinking section, with an option to write a standalone challenge report into the concepts folder.
Without references/ai-first-rules.md accessible in the path hierarchy, the command warns you before saving because all generated files require strict agent-readable schemas.
What it helps with
- stress-test a new project idea against personal vault history
- locate past failures and dev log lessons relevant to a current plan
- extract contradictory arguments from older decisions and notes
- log critical analysis directly into the daily note
Example prompts for the agent
- /obsidian-challenge Switch the primary database to Postgres
- /obsidian-challenge
- stress test this plan against my vault
How to install obsidian-challenge
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-challenge.mdCall it with /obsidian-challenge. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-challenge.mdCall it with /prompts:obsidian-challenge. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-challenge.prompt.mdManually: put the files in place
.gemini/commands/obsidian-challenge.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-challenge
How to install obsidian-challenge in Claude Code?
Add the marketplace source via /plugin marketplace add eugeniughelbur/obsidian-second-brain and install the package with /plugin install obsidian-second-brain@obsidian-second-brain. The definition resides at .claude/commands/obsidian-challenge.md.
What does obsidian-challenge do?
It runs a counter-analysis on your proposal using parallel search subagents that scan your vault for past mistakes and opposing decisions.
What files must exist in the Obsidian vault for this command?
It relies on references/ai-first-rules.md for output schemas and references/folder-map.md for target folders, while reading _CLAUDE.md from the vault root if available.
Source text
obsidian-challenge.md · MIT
--- description: Red-team your current idea against your own vault history - finds contradictions, past failures, and flawed assumptions category: thinking triggers_en: ["challenge this", "grill me on this", "red team my idea", "stress test this"] triggers_de: ["stell das infrage", "nimm mich dazu in die Mangel", "prüfe meine Idee kritisch", "mach einen Stresstest dafür"] triggers_es: ["cuestiona esta idea", "ponme a prueba con esto", "haz de abogado del diablo con mi idea", "pon esto a prueba", "dime por qué esto no funcionaría"] triggers_pt: ["desafie isto", "questione minha ideia", "faça um red team da minha ideia", "teste esta ideia"] triggers_zh: ["挑战一下这个想法", "帮我找这个方案的问题", "站在反方审视它", "给这个想法做压力测试", "别客气地质疑我"] --- Use the obsidian-second-brain skill. Execute `/obsidian-challenge $ARGUMENTS`: The optional argument is the idea, belief, or plan to challenge. If not provided, infer the user's current position from conversation context. 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Identify the user's current claim, plan, or assumption - either from the argument or from recent conversation 3. Extract the key premises behind that position 4. Search the vault for counter-evidence - spawn parallel subagents: - **Decisions agent**: search Key Decisions sections in project notes for past decisions that contradicted or reversed similar thinking - **Failures agent**: search dev logs, daily notes, and archives for past failures, regrets, or lessons learned related to this topic - **Contradictions agent**: search for notes where the user held the opposite position or flagged risks about this exact approach 5. Synthesize a structured "Red Team" analysis: - **Your position**: restate the claim clearly - **Counter-evidence from your vault**: cite specific notes, dates, and quotes - **Blind spots**: what the user might be ignoring based on their own history - **Verdict**: is this position consistent with past experience, or does the vault suggest caution? 6. Log the challenge in today's daily note under a Thinking section 7. Offer to save the full challenge report as a standalone note in the concepts/ideas folder (resolved per `references/folder-map.md`), `type: challenge`, thinking-tool schema in `references/ai-first-rules.md` Do not be agreeable. The entire point is to pressure-test. Cite specific vault files. If you find nothing contradictory, say so honestly - but search thoroughly first. --- **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