replace todo.md references with vik CLI across daily-briefing, shutdown-routine, weekly-review

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

weekly-review/SKILL.md

@@ -32,7 +32,7 @@ Work through the two parts in order.
 
 1. Find this week's note at `~/notes/week_YYMMDD.md` (current week's Monday date).
 2. Read the goals/tasks that were set for the week.
-3. Read `~/notes/todo.md` to check what got done.
+3. Run `vik task list` to see the current task state and check what got done.
 4. Present a summary:
 
 **Week in Review — [Week of Month Day–Month Day]**
@@ -41,7 +41,7 @@ Work through the two parts in order.
 [The goals/tasks set in the week note at the start of the week.]
 
 **Accomplished**
-[What got done. Cross-reference the week note goals with todo.md completions.]
+[What got done. Cross-reference the week note goals with tasks visible in `vik task list`.]
 
 **Incomplete**
 [Goals that didn't get finished. No judgment — just facts.]
@@ -87,8 +87,8 @@ Ask: "Anything from this week you want to carry into next week?"
 
 - Always do both parts. Don't let the session end without creating the new week note.
 - The reflection questions are conversational — ask them, wait, don't skip or auto-fill.
-- If this week's note doesn't exist (e.g., it was never created), work from todo.md and ask what the goals were.
-- Carry-forward tasks should be added to todo.md, not just mentioned.
+- If this week's note doesn't exist (e.g., it was never created), run `vik task list` for context and ask what the goals were.
+- Carry-forward tasks should be created with `vik task create`, not just mentioned.
 - Keep the whole session focused. If it's running long, it's okay to timebox the planning step.
 
 ---