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

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

daily-briefing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: daily-briefing
-description: Morning briefing that pulls today's tasks from ~/notes/todo.md and gives a clear picture of what's on deck.
+description: Morning briefing that pulls today's tasks from Vikunja via vik and gives a clear picture of what's on deck.
 triggers:
   - run my briefing
   - morning briefing
@@ -18,28 +18,26 @@ Run this at the start of your day.
 
 ## Instructions
 
-1. Read `~/notes/todo.md`.
-2. Identify tasks marked for today or with no specific date (treat undated tasks as fair game for today).
-3. Identify any overdue tasks (past their date if dated).
-4. Produce the briefing below.
+1. Run `vik task today` to get tasks due or starting today.
+2. Run `vik task upcoming` to get tasks coming up later this week.
+3. Produce the briefing below.
 
 ### Output Format
 
 **Daily Briefing — [Weekday, Month Day]**
 
 **Today's Tasks**
-[Tasks from todo.md that are due today or are undated and in progress. Numbered list.]
+[Tasks from `vik task today`. Numbered list.]
 
 **Overdue**
 [Any tasks past their due date. Flag these clearly.]
 
 **Later This Week**
-[Tasks with future dates this week, so you know what's coming.]
+[Tasks from `vik task upcoming` with future dates this week.]
 
 ## Rules
 
 - Keep it scannable. Short lines, clear sections.
-- If todo.md doesn't exist yet, say so and offer to create it.
 - Don't editorialize. Present the tasks as written. Let Connor decide priorities.
 - Overdue items always appear, even if the list is long.
 - If there are no tasks in a section, omit that section header.

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.
 
 ---
 

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.
 
 ---