alirezarezvani/weekly-review

Weekly Review — GTD Loop → Trusted System

Portability: Reasoning-led skill with 3 stdlib Python scripts. No external APIs, no LLM calls in scripts. Works in Claude Code CLI and Claude.ai web. The scripts do the inventory and the gating; Claude and the user do the thinking.

What this does

A personal system is only trustworthy if it gets reviewed — David Allen calls the weekly review the critical success factor of the whole method. This skill walks the three phases in order and refuses to call the review COMPLETE while any of the five mandatory GET CURRENT steps is unaccounted for. Evidence first: scan the workspace for open loops before asking the user to recall anything, because their memory is exactly what the method says not to trust.

Phase 1 — GET CLEAR (steps 1-3)

Collect loose inputs, process every inbox to zero (clarify, don't do — anything over two minutes becomes a next action), then a mind sweep to empty the head. Start with evidence:

# Inventory open loops: unchecked checkboxes, TODO/FIXME markers, stale files
python scripts/open_loop_scanner.py --dir ~/notes --stale-days 14

Route every loop found to a list — next action, waiting-for, someday/maybe, or trash.

Phase 2 — GET CURRENT (steps 4-8, all mandatory)

Review the next-action lists (mark done, prune dead), the previous calendar (missed commitments become actions), the upcoming calendar (prepare, don't react), the waiting-for list (chase or drop), and every project for exactly one next action. Then gate honestly:

python scripts/weekly_review_gate.py --list   # show the numbered ten-step checklist
python scripts/weekly_review_gate.py --done "1,2,3,4,5,6,7,8" --skip "9:no someday list yet"

The gate computes completion %, names every missing step, and exits 0 (COMPLETE) or 2 (INCOMPLETE). An unskipped missing GET CURRENT step always forces INCOMPLETE.

Phase 3 — GET CREATIVE (steps 9-10)

Review someday/maybe (activate, keep, or kill), capture new ideas while the head is clear, then audit the whole commitment portfolio:

python scripts/commitment_auditor.py --input commitments.json

Flags STALLED / NO-NEXT-ACTION / SOMEDAY-CANDIDATE, prints the health formula with the score, and issues HEALTHY / DRIFTING / OVERCOMMITTED. End the review with one named next action.

Scripts

| Script | Role | |---|---| | scripts/open_loop_scanner.py | Inventories unchecked checkboxes, TODO/FIXME markers, and stale files across a directory; grouped counts + per-file locations; --json. | | scripts/weekly_review_gate.py | The ten-step three-phase checklist; --done/--skip/--list; completion % + named gaps → COMPLETE (exit 0) / INCOMPLETE (exit 2). | | scripts/commitment_auditor.py | Flags stalled and actionless commitments, computes the 0-100 health score with the formula shown → HEALTHY / DRIFTING / OVERCOMMITTED. |

References

• references/gtd_weekly_review_canon.md — why the weekly review is the critical success factor; the three-phase structure; cadence discipline (7 sources)
• references/open_loop_psychology.md — Zeigarnik effect, plan-making research, attention residue: why open loops tax attention (6 sources)
• references/review_cadence_design.md — horizons of focus, habit anchoring, timeboxing, failure modes, restart-after-lapse (7 sources)

Assets

• assets/weekly_review_checklist.md — fillable three-phase checklist
• assets/example_weekly_review.md — a full worked review (scan → checklist → gate → audit → next action)

Rules

• All five GET CURRENT steps are mandatory; skip only with a stated reason, and the gate still names it.
• Never self-certify — the gate issues the verdict; relay its exit code, don't soften it.
• Process, don't do: during the review, anything over two minutes becomes a next action, not a detour.
• Timebox 60-90 minutes; past two hours, gate what's done honestly and schedule the remainder.
• A lapsed habit restarts with a shorter pass and zero guilt — a review is maintenance, not judgment.

Distinct From (don't reach for the wrong sibling)

• productivity/reflect — reflects on one conversation or piece of work, once. The weekly review is a recurring cadence over the whole system.
• productivity/capture — the intake funnel (brain dump → actions). Capture feeds the system; this review keeps it trusted.
• project-management sprint retros — a team ceremony about a shared iteration. This is a personal trusted-system audit.

---

Version: 1.0.0 · Build pattern: Path-B ritual skill — GTD weekly-review loop preserved + deterministic gate/scanner/auditor scripts added.