From obsidian-operator
TRIGGER for /annual-vision, or when the user wants to set their annual vision, define yearly goals, conduct a year-end retrospective, or set strategic direction for the upcoming year. NOT for quarterly/monthly/weekly planning or multi-year career plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-operator:annual-visionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Annual vision setting and year-end retrospective.
Annual vision setting and year-end retrospective.
[year] — target year. Default: current year.review — run in retrospective mode instead of vision-setting.Auto-detect: if 00_Strategy/YYYY Vision.md exists and it's December → review mode. Otherwise → vision mode.
00_Strategy/YYYY Vision.md (if exists — this becomes the baseline for updating rather than starting from scratch)02_Projects/If an existing Vision file was read in Step 1, present the current goals, bets, and themes to the user for review. Ask which items to keep, update, or remove before asking for new additions. Otherwise, ask the user one question at a time:
Write (or update) 00_Strategy/YYYY Vision.md using the template. If updating an existing file, preserve structure and merge changes from the discussion.
Run obsidian open path="00_Strategy/YYYY Vision.md" to open the file in Obsidian.
00_Strategy/YYYY Vision.md — what was envisioned00_Strategy/YYYY Annual Review.md (if exists — use as starting point to enrich rather than replace)02_Projects/Write (or update) 00_Strategy/YYYY Annual Review.md using the template. If updating an existing file, preserve existing assessments and enrich with new analysis.
Run obsidian open path="00_Strategy/YYYY Annual Review.md" to open the file in Obsidian.
npx claudepluginhub yuhanwang14/obsidian-operator --plugin obsidian-operatorGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.