Use vik t done 7 for weekly review to capture full week of completed tasks

weekly-review/SKILL.md

@@ -34,7 +34,7 @@ This part is backward-looking only. Focus on what happened, not what's coming.
 
 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. Run `vik task done` to see what tasks were completed this week.
+3. Run `vik t done 7` to see what tasks were completed in the last 7 days.
 4. Present a summary:
 
 **Week in Review — [Week of Month Day–Month Day]**
@@ -43,7 +43,7 @@ This part is backward-looking only. Focus on what happened, not what's coming.
 [The goals/tasks set in the week note at the start of the week.]
 
 **Accomplished**
-[What got done. Use `vik task done` output to cross-reference against week note goals.]
+[What got done. Use `vik t done 7` output to cross-reference against week note goals.]
 
 **Incomplete**
 [Goals that didn't get finished. No judgment — just facts.]
@@ -92,10 +92,10 @@ This part looks forward. Use `vik t up` to see what's on deck.
 
 - 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), use `vik task done` for context and ask what the goals were.
+- If this week's note doesn't exist (e.g., it was never created), use `vik t done 7` 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.
-- Part 1 is backward-looking: use `vik task done` to see what was completed. Do NOT use `vik t up` here.
+- Part 1 is backward-looking: use `vik t done 7` to see what was completed. Do NOT use `vik t up` here.
 - Part 2 is forward-looking: use `vik t up` to show what's due/starting soon. Do NOT pull in the full `vik task list`.
 
 ---