메뉴
Takes raw unstructured thoughts, voice transcript dumps, or stream-of-consciousness text and auto-files them into the right Obsidian vault folders with tags, backlinks, and proper frontmatter. Use when the user says "braindump", "brain dump", "capture this", "dump my thoughts", "I'm thinking about...", or provides a long unstructured block of text to organize.
Strategy & Decision Intelligence — 8 skills for personal productivity, strategic thinking, and decision-making. Pre-mortem risk analysis, braindump capture to Obsidian vault, morning briefings, priority drift detection, strategy red-teaming, multi-audience stakeholder updates, structured decision logging, and weekly reviews. All skills integrate with the Obsidian vault and knowledge-graph-memory for persistent context. Use when: (1) planning or evaluating a project, (2) capturing thoughts or decisions, (3) generating briefings or reviews, (4) checking strategic alignment, (5) user says "pre-mortem", "braindump", "morning briefing", "drift check", "strategy critique", "stakeholder update", "decision log", "weekly review".
Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: 'premortem this', 'premortem my', 'run a premortem', 'what could kill this', 'future-proof this', 'stress test this plan', 'what am i missing here', 'find the blind spots'. STRONG TRIGGERS: 'what could go wrong', 'am i missing anything', 'poke holes in this', 'where will this break', 'devil's advocate this'. Do NOT trigger on simple feedback requests, factual questions, or LLM Council requests. DO trigger when someone has a plan or commitment where the cost of being wrong is high.
Captures a decision with context, alternatives considered, and rationale, then links it to the relevant project doc in the vault. Creates a searchable decision record. Use when the user says "decision log", "log this decision", "record this choice", "document why we chose", "decision record", "ADR", or has just made an important decision.
Compares stated priorities against where time and effort actually went, and produces a strategy drift report. Uses git log, vault priorities, and project docs to detect misalignment. Use when the user says "drift check", "am I on track", "priority alignment", "where did my time go", "strategy drift", or wants to audit focus vs intention.
Reads open action items, this week's priorities, and recent vault updates, then produces a focused "start your day" brief. Use when the user says "morning briefing", "daily brief", "what's on my plate", "start my day", "what should I focus on today", or at the start of a work session.
Assumes a project has already failed, works backward to identify the top causes, scores them by likelihood and impact, and outputs a mitigation plan. Use when starting a new project, before a major launch, evaluating risky decisions, or when the user says "pre-mortem", "what could go wrong", "risk analysis", "failure modes", "red team this plan".
| name | braindump |
| description | Takes raw unstructured thoughts, voice transcript dumps, or stream-of-consciousness text and auto-files them into the right Obsidian vault folders with tags, backlinks, and proper frontmatter. Use when the user says "braindump", "brain dump", "capture this", "dump my thoughts", "I'm thinking about...", or provides a long unstructured block of text to organize. |
Turn messy thoughts into organized vault entries.
Receive raw input — Accept any unstructured text: stream-of-consciousness, voice transcript, bullet points, mixed topics, rambling notes. Do not ask the user to organize it first.
Extract discrete topics — Parse the input and identify distinct topics, ideas, or threads. Each becomes a separate note or gets appended to an existing note.
Classify each topic — Determine the best vault location:
projects/ideas/- [ ] checkbox, link to relevant projectdecisions/ with decision-log formatreferences/ or relevant project's docs/journal/references/technical/meetings/Generate backlinks — For each note, identify:
[[wikilink]] syntax)#project-name, #idea, #decision)[[People/Name]]Write frontmatter — Each note gets:
---
type: braindump
source: [user-input | voice-transcript | meeting]
date: [YYYY-MM-DD]
topics: [list of extracted topics]
tags: [relevant tags]
---
Present summary — Show the user what was created:
## Braindump Processed
**Input**: [brief description of what was provided]
**Date**: [YYYY-MM-DD]
### Notes Created
1. `projects/ideas/[topic].md` — [one-line summary]
2. `references/technical/[topic].md` — [one-line summary]
### Action Items Extracted
- [ ] [action] → linked to [[Project]]
- [ ] [action] → linked to [[Project]]
### Backlinks Established
- [[Existing Note]] ← new connection from [topic]
Default vault: ~/broomva-vault/
If the vault is not accessible, output the notes as markdown blocks the user can manually save.
inbox/ and tag for later sorting