Separate weekly review into backward-looking and forward-looking parts
Part 1 (review) now uses vik task done only. Part 2 (planning) uses vik t up to show upcoming tasks instead of dumping the full task list.
This commit is contained in:
parent
7b59a9d8ee
commit
15e7e48cbb
1 changed files with 15 additions and 8 deletions
|
|
@ -30,9 +30,11 @@ Work through the two parts in order.
|
||||||
|
|
||||||
### Part 1: Review the Closing Week
|
### 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).
|
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.
|
2. Read the goals/tasks that were set for the week.
|
||||||
3. Run `vik task list` to see the current task state and check what got done.
|
3. Run `vik task done` to see what tasks were completed this week.
|
||||||
4. Present a summary:
|
4. Present a summary:
|
||||||
|
|
||||||
**Week in Review — [Week of Month Day–Month Day]**
|
**Week in Review — [Week of Month Day–Month Day]**
|
||||||
|
|
@ -41,7 +43,7 @@ Work through the two parts in order.
|
||||||
[The goals/tasks set in the week note at the start of the week.]
|
[The goals/tasks set in the week note at the start of the week.]
|
||||||
|
|
||||||
**Accomplished**
|
**Accomplished**
|
||||||
[What got done. Cross-reference the week note goals with tasks visible in `vik task list`.]
|
[What got done. Use `vik task done` output to cross-reference against week note goals.]
|
||||||
|
|
||||||
**Incomplete**
|
**Incomplete**
|
||||||
[Goals that didn't get finished. No judgment — just facts.]
|
[Goals that didn't get finished. No judgment — just facts.]
|
||||||
|
|
@ -57,12 +59,15 @@ Ask: "Anything from this week you want to carry into next week?"
|
||||||
|
|
||||||
### Part 2: Plan the New 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.
|
1. Calculate the upcoming Monday's date.
|
||||||
2. Create `~/notes/week_YYMMDD.md` for the new week using the template below.
|
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. Ask: "What are your goals for this week? What tasks do you want to make sure happen?"
|
3. Create `~/notes/week_YYMMDD.md` for the new week using the template below.
|
||||||
4. Take the response and populate the Goals section of the new week note.
|
4. Ask: "What are your goals for this week? What tasks do you want to make sure happen?"
|
||||||
5. Ask: "Anything else to note going into the week? Deadlines, commitments, things to watch for?"
|
5. Take the response and populate the Goals section of the new week note.
|
||||||
6. Add those to the Notes section.
|
6. Ask: "Anything else to note going into the week? Deadlines, commitments, things to watch for?"
|
||||||
|
7. Add those to the Notes section.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -87,9 +92,11 @@ 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.
|
- 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.
|
- 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), run `vik task list` for context and ask what the goals were.
|
- 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.
|
||||||
- Carry-forward tasks should be created with `vik task create`, not just mentioned.
|
- 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.
|
- 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 2 is forward-looking: use `vik t up` to show what's due/starting soon. Do NOT pull in the full `vik task list`.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue