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.