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

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

shutdown-routine/SKILL.md

@@ -24,12 +24,12 @@ Work through these four steps in order. Each step is conversational — ask, wai
 
 ### Step 1: Accomplishments
 
-Read `~/notes/todo.md` and identify any tasks that were completed today (or ask Connor what he got done if the file doesn't reflect completions clearly).
+Run `vik task today` to see what was on the plate for today, then ask Connor what he got done.
 
 Present what was accomplished:
 
 **Completed Today**
-[List of tasks finished. If nothing is marked done, ask: "What did you get done today?"]
+[List of tasks Connor confirms finishing. Mark each done with `vik task update <ID> --done`.]
 
 ---
 
@@ -63,13 +63,13 @@ Say:
 
 > "Let's plan tomorrow. What tasks do you want to tackle?"
 
-Take their input and update `~/notes/todo.md` with tomorrow's tasks. Add a date marker or "tomorrow" label so they're easy to find in the morning briefing.
+Take their input and create each task with `vik task create "Task title" d+1` so they show up in tomorrow's briefing.
 
 **Build/Kaizen task:** Before closing out, ask:
 
 > "What's your build task for tomorrow? One thing that will make you more productive in the future."
 
-Add it to todo.md labeled as `[build]`.
+Add it with `vik task create "Task title" d+1 --label build`.
 
 ---
 
@@ -79,7 +79,7 @@ Add it to todo.md labeled as `[build]`.
 - Keep the whole routine under 10 minutes. If a step is going long, gently redirect.
 - Don't create tasks beyond what Connor asks for. Just capture what he says.
 - Always end with the build/kaizen task. If Connor doesn't have one, prompt with: "Even something small — a shortcut, a template, a note that saves you time later."
-- Write tasks to todo.md, don't just echo them back.
+- Create tasks in Vikunja with `vik task create`, don't just echo them back.
 
 ---