메뉴
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.
| name | morning-briefing |
| description | 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. |
Produce a focused daily brief to start the day.
Scan open action items — Search the vault for unchecked tasks (- [ ]):
Check this week's priorities — Look for:
weekly-plan.md or weekly-review-*.md in the vaultScan recent vault changes — Check files modified in the last 24 hours:
Check git activity — Run git log --since="yesterday" --oneline across active repos to surface:
Compose the brief — Organize into a scannable format.
## Morning Briefing — [Day, YYYY-MM-DD]
### Focus Today
1. [Top priority — why it matters]
2. [Second priority]
3. [Third priority]
### Open Action Items ([count] total)
**Overdue**
- [ ] [item] — from [[source note]] (due [date])
**Due Today**
- [ ] [item] — from [[source note]]
**This Week**
- [ ] [item] — from [[source note]]
### What Changed Yesterday
- [vault change or git activity summary]
- [vault change or git activity summary]
### Heads Up
- [Anything requiring attention: upcoming deadlines, blocked items, meetings]
~/broomva-vault/ (all folders)journal/briefing-[YYYY-MM-DD].mdStrategy & 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.
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.
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.
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".
