Agent skill · operations · alirezarezvani
weekly-review
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs-weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
Why this skill is useful
Adds three executable Python scripts for automating the weekly review process, which are not commonly available in public documentation.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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: 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: 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: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/weekly-review--2b79dc