92 lines
3.3 KiB
Markdown
92 lines
3.3 KiB
Markdown
---
|
||
name: weekly-review
|
||
description: Single weekly session (typically Sunday) that reviews the closing week and plans the new one. Creates a week note for the new week at the end.
|
||
triggers:
|
||
- weekly review
|
||
- how'd my week go
|
||
- plan my week
|
||
- Sunday review
|
||
---
|
||
|
||
# Weekly Review
|
||
|
||
One session does it all: close out the week, reflect, and plan the next one.
|
||
|
||
## When to Use
|
||
|
||
Run this on Sunday (or Saturday if Sunday is busy). Do both parts in a single session.
|
||
|
||
## Week Note File Naming
|
||
|
||
Week notes live at `~/notes/week_YYMMDD.md` where YYMMDD is the date of that week's **Monday**.
|
||
|
||
Example: a week starting Monday April 7, 2026 → `~/notes/week_260407.md`
|
||
|
||
## Instructions
|
||
|
||
Work through the two parts in order.
|
||
|
||
---
|
||
|
||
### Part 1: Review the Closing Week
|
||
|
||
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 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]**
|
||
|
||
**Goals This Week**
|
||
[The goals/tasks set in the week note at the start of the week.]
|
||
|
||
**Accomplished**
|
||
[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.]
|
||
|
||
**Carry Forward?**
|
||
Ask: "Anything from this week you want to carry into next week?"
|
||
|
||
5. Ask two reflection questions (conversational — wait for each answer):
|
||
- "How did the week go overall?"
|
||
- "Anything you'd do differently next week?"
|
||
|
||
---
|
||
|
||
### Part 2: Plan the New Week
|
||
|
||
This part looks forward. Use `vik t up` to see what's on deck.
|
||
|
||
1. Calculate the upcoming Monday's date.
|
||
2. Run `vik t up` to show tasks due or starting in the past or next 7 days. Present this as context for planning.
|
||
3. Create `~/notes/week_YYMMDD.md` for the new week using the template below.
|
||
4. Ask: "What are your goals for this week? What tasks do you want to make sure happen?"
|
||
5. Take the response and populate the Goals section of the new week note.
|
||
5. Ask: "Anything else to note going into the week? Deadlines, commitments, things to watch for?"
|
||
6. Add those to the Notes section.
|
||
|
||
---
|
||
|
||
## Notes
|
||
|
||
If Connor gives a philosophical or reflective answer (e.g., "take it easy," "focus on what matters," "be present"), put it in *italics* at the very top of the Notes section, before any practical items. Do not respond with matching philosophical language. Just acknowledge and add it to the note.
|
||
|
||
---
|
||
|
||
## Rules
|
||
|
||
- 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 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 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`.
|
||
|
||
---
|
||
|
||
*Customized in Video 7 via the assembler.*
|