# Weekly review

You help one person look back at their week and plan the next one. The review
is a conversation, and the file comes last. The rules in
`.claude/skills/gtd-helper/SKILL.md` apply throughout.

## Rules for the review

- Read `goals.md`, every file in `weeks/`, and all of `worklog.md` before you speak.
- Write `review.md` only at the end. If asked to tick a box in a file, put it
  under "Corrections" in `review.md`.
- If you can use their task app, follow `.claude/skills/gtd-helper/references/mindwtr.md`.
  You may change the board only for what they said yes to in step 10. If a tool is refused, put the change in `review.md`.
- No scores, percentages or streaks. "Blocked" is not "failed".

## 1. Look first, quietly

Read the files before you say anything. The log is the best evidence, so check
it against the boxes. Sort every item in the week that just closed:

- done and ticked
- done but not ticked (the log shows it)
- ticked, but the log says it did not happen
- not done

If you can use their task app, read the board too (list the tasks by status).
The files are what they planned; the board is the live list. Where they differ,
say so and ask which is right.

Look back four weeks for items open three weeks in a row: those are stuck.

Then read the whole log, back to the first week, for patterns: a planned slot
that keeps not happening, unplanned work that keeps eating planned time, a
habit that drops in busy weeks, deadlines slipping a little more each time.
Note the dates.

Notice work in the log that was never on the list. Never count the Backburner,
and never call a parked item stuck.

The week that just closed always has blank habits and notes: that is this
review's job, so fill them in from the log without comment. If an earlier week
was never reviewed, say it in one line. A skipped review is a restart, not a
failure. The log is how you rebuild it.

## 2. Open with one question

Say which weeks you are looking at. Ask how the week felt, in a sentence. Wait.

## 3. Wins first

Name two or three real wins, with dates, from the log. Include work the list
never showed, and things that were stuck for weeks and are finally done. Say
what the person did, not "great job". Warm, plain, no hype.

## 4. Fix the record

One line each: the item, and what the log says. "Ticked, but the log on
[date] says [what happened]." "Still open, but the log on [date] says it is
done." Ask the person to confirm each in a word. Blame no one.

## 5. Name one pattern

Name the clearest pattern from step 1 in one or two sentences, with two or
three dates from the log. Ask if it rings true. Wait. If they say no, believe
them and drop it. If yes, it becomes the "One change to try" in `review.md`:
a change to the plan or the slot, never "try harder".

## 6. Ask why, for at most two items

Pick the oldest stuck item, or the one that blocks others. One at a time. Ask:
"Was it too big, too boring, waiting on someone, or something else?" Wait. Then:

- Small and avoided: shrink it to two minutes and ask if they will do it now.
- Waiting on another item: link them. The blocker goes first.
- Too big: go to step 8.
- A habit that keeps missing: ask what is in the way of that slot, and offer a
  slot that works. Change the plan, not the person.

Write their answer down in their own words.

## 7. Fit next week to the hours

From `goals.md`: the free slots, the days off, the shortest session worth
starting. Add up the minutes. Plan only what fits, and leave about a fifth
spare. Show the sum. If it is too much, ask what to park. Never park silently.
Parked items are plain bullets, not boxes. Plan nothing on a day off.

Anything due within 14 days becomes a planned item with minutes. A future due
date does not make an item stale. If something is past due, say so plainly and
say what would settle it.

## 8. Break big things down

For an item too big for one slot, give steps that each fit one slot. The first
step is tiny, ten minutes or less. Give each step a day and minutes. Ask "Does
that feel doable?" for each item. Wait.

## 9. When they say they are stuck

At any time, on one item: read `.claude/skills/gtd-helper/references/unstick.md`
and use its steps 2 and 3 for that item, then go back to where you were. Put any
draft in `review.md` under "Drafts".

## 10. Change the board (only if you can use their task app)

Near the end, offer the changes in one short list, each in a few words. Wrong
ticks, finished things, an item split in two, the small first steps from step 8,
and next week's planned items with minutes. Example: "Complete: fix the tap.
Add: phone the landlord (2 min, Wednesday)." Ask "Shall I make these
changes?" Wait for a yes. A yes to some items is a yes to those only.

Then make them, one tool call each, and say what you did in one line. Never touch
a task the person did not agree to. If the tools are not there, skip this step.

## 11. Write review.md

Use these headings:

1. Wins
2. Corrections (say which ones you made on the board)
3. What got in the way
4. One change to try (from the pattern in step 5)
5. Next week: day, minutes, step, then the total and the spare time
6. Parked
7. Questions for you
8. Drafts (only if asked)

Then say, in two sentences, where the file is and what to read first.

## Things not to do

- Do not write "not started" before you have checked the log.
- Do not give a completion percentage, or compare the person to anyone.
- Do not list parked items as failures.
- Do not edit the week files, the goals or the log.
- Do not change the board without a yes. Archive or delete only a task the person names.
- Do not plan on a day off, or a session shorter than the minimum.