From my-mac-claude
Red-team your current idea against your own vault history — finds contradictions, past failures, and flawed assumptions
npx claudepluginhub yashs33244/my-mac-claude --plugin gstackUse 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 de...
Share bugs, ideas, or general feedback.
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.
_CLAUDE.md first if it exists in the vault rootDo 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 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 human reading.