review

/review

Guided weekly review. This is GTD's Reflect stage and the main place drift is caught and corrected. Keep it ≤30 minutes — a review the user dreads won't happen.

Flow

0. Sync

git -C ${GTD_VAULT:-$HOME/gtd} pull --rebase --autostash 2>&1 | tail -3

1. Setup

TODAY=$(TZ=Asia/Tokyo date +%Y-%m-%d)
WEEK=$(TZ=Asia/Tokyo date +%G-W%V)    # ISO week, e.g. 2026-W17

Target file: reviews/weekly/{WEEK}.md. If it exists, ask 今週のレビューは既にあります。(a) 続きから (b) 上書き (c) 中止.

Create from templates/weekly-review.md (fill {{date:GGGG-[W]WW}} → {WEEK}, {{date:YYYY-MM-DD}} → {TODAY}).

2. Walk through the checklist

Address each section ONE AT A TIME. After each, update the corresponding checkbox / section in the review file.

2-1. Clear inbox

N=$(ls ${GTD_VAULT:-$HOME/gtd}/gtd/inbox/*.md 2>/dev/null | grep -v /.gitkeep$ | wc -l)

• If N > 0: offer to run /inbox first. If the user declines, note "inbox: N件残 (意図的に後回し)".
• If N = 0: check the box ✓.

2-2. Fleeting Zettels

ls ${GTD_VAULT:-$HOME/gtd}/zettelkasten/fleeting/*.md 2>/dev/null | grep -v /.gitkeep$ | wc -l

Ask if any should be promoted via /zettel. Same offer-or-defer pattern.

2-3. Review next-actions

List all in gtd/next-actions/. For each, check:

• created > 14 days old → ask: "まだ関連ある？(keep/drop/change-context)"
• due in past → ask: "延期？完了？キャンセル？" Update files as user directs (move to finished/, delete, or edit frontmatter).

2-4. Review projects

For each in gtd/projects/:

• Check it has at least one next-action file with project: [[{name}]]
• If not → ask for a next action → create it in next-actions/
• Ask if project is still active, done, or paused (status: frontmatter)
• If done: move to finished/ (or a projects/archive/)

2-5. Review waiting-for

For each in gtd/waiting-for/:

• expected_by past or near → ask "still waiting? chase? give up?"

2-6. Review someday-maybe

Ask the user to eyeball gtd/someday-maybe/ (you list the filenames). For any that have become actionable, ask to promote to projects/ or next-actions/.

2-7. Calendar check

Can't read calendar. Just remind: "先週と次2週間のカレンダーを見てください。" Wait for user to confirm "確認した".

3. Reflect

Ask in sequence:

うまくいったこと (1-3個):
うまくいかなかったこと (1-3個):
来週のフォーカス (1-3個):

Multi-line input accepted. Fill into the "## 3. 振り返り" and "## 4. 来週のフォーカス" sections.

4. Write review file + offer to commit

Write the filled-in review to reviews/weekly/{WEEK}.md.

Show git status --short. Ask レビューと関連するファイル変更を全部コミットしますか？ (y/n). If yes:

git -C ${GTD_VAULT:-$HOME/gtd} add -A
git -C ${GTD_VAULT:-$HOME/gtd} commit -m "review: {WEEK}"

Don't push.

Rules

• Keep the user moving. If they start deep-diving on a single item, gently suggest capturing it as a new next-action and coming back later.
• Never skip inbox clearing without noting it — undealt-with inbox is the #1 source of GTD collapse.
• Don't silently delete items. Every removal must have user confirmation.
• Offer, don't force. If the user wants to skip sections 2-3 through 2-6 ("just reflect"), allow it and note "depth: surface" in the review file.
• Keep under 30 min. Track time implicitly — if the conversation is ballooning, ask "ここで一旦切って来週のフォーカスだけ決める？"