challenge-decision

Pressure-tests decisions against vault history and runs postmortems on reversed decisions.

Updated May 22, 2026
One-click install
npx skills add https://github.com/fbureau/second-brain --skill challenge-decision-fbureau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: challenge-decision
Source: https://github.com/fbureau/second-brain/tree/main/.claude/skills/challenge-decision
Command: npx skills add https://github.com/fbureau/second-brain --skill challenge-decision-fbureau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? High-stakes decisions are often made under confirmation bias, repeating past failure patterns that already exist in your own notes. This Skill forces every major decision to be checked against your Obsidian vault's recorded history before you commit, and turns reversed decisions into durable lessons instead of silent failures. ## Core Features & Use Cases - Red-team mode (pre-decision): Frames the decision, searches decisions, meetings, people, and knowledge notes for counter-evidence, blind spots, and repeated failure patterns, then delivers an honest verdict (supports, warns, or vault-silent) with mandatory citations. - Postmortem mode (post-reversal): When a decision flips to status reversed, extracts the failed hypothesis, cross-references every wiki, lesson, decision, and project that rests on it, and proposes batched append-only corrections for human approval. - Structured artifacts: Writes a challenge analysis note in 05-decisions/ or a postmortem note in 06-knowledge/, propagates a summary to the daily note, and supports auto-triggering from daily-brief with human-in-the-loop edits. - Use Case: Before committing to centralizing a support team, ask for a challenge; the Skill cites two prior reversed centralization decisions and a stakeholder's recorded opposition, producing a warns verdict with questions to resolve first. ## Quick Start Ask the assistant to red-team the decision you are considering against your vault before you commit to it.

Frequently Asked Questions about challenge-decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress test a decision against my past notes?▼

Invoke the red-team mode by saying challenge this or red team before committing. The Skill frames the decision, searches your vault's decisions, meetings, people, and knowledge notes, then returns a cited verdict of supports, warns, or vault-silent.

What happens when a decision gets reversed in the vault?▼

The postmortem mode extracts the failed hypothesis, finds every wiki, lesson, decision, and project that relied on it, and proposes batched append-only corrections. Edits are previewed first and only applied after your approval.

Can daily-brief trigger a postmortem automatically?▼

Yes. When daily-brief detects a decision note flipped to status reversed, it runs the postmortem analysis and cross-referencing automatically, but stops before applying edits. Proposed changes appear in the brief marked needs-review for your manual approval.

When should I not use decision red-teaming?▼

Skip it for trivial topics, purely technical questions about code or configuration, and decisions already committed and executing successfully. In those cases answer normally or log the update with meeting-ingest or people-update instead.

What if my vault has no history on the decision topic?▼

The Skill honestly reports a vault-silent verdict instead of inventing contradictions. It suggests adjacent patterns that may be relevant and recommends logging the decision so it can be challenged later.