Weekly Review — GTD Loop → Trusted System — Productivity

This skill runs a full GTD weekly review through David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — using deterministic scripts to inventory open loops, gate the checklist, and audit commitment health. It produces a verdict (COMPLETE/INCOMPLETE) and a health score, ensuring your personal system stays trusted.

productivity claude-code

📂 View skill on GitHub ↗ 🚀 How to use

✨ What it does

Scans a directory for open loops (unchecked checkboxes, TODO/FIXME markers, stale files).
Walks the ten-step three-phase checklist with a gate that computes completion and names missing steps.
Audits commitments, flagging stalled or actionless items and scoring health 0-100.
Enforces all five GET CURRENT steps as mandatory; skips require a stated reason.
Provides references and assets for GTD principles and a fillable checklist.
Timeboxes the review to 60-90 minutes and handles lapsed habits with a shorter pass.

🎯 When to use it

When you want to run a weekly review to close open loops and get your system back to trusted.
When you need to audit stalled projects or commitments and identify next actions.
When you've lapsed your review habit and want to restart with a structured, guilt-free process.
When you say '/cs:weekly-review' to trigger the skill.

🚀 How to use

Trigger with '/cs:weekly-review' or a request like 'Run my weekly review'. Optionally provide a directory or notes to review. The skill runs three scripts: open_loop_scanner.py, weekly_review_gate.py, and commitment_auditor.py. Example prompts:

/cs:weekly-review
Run a weekly review on ~/notes and audit my commitments.

📄 Output: A review verdict (COMPLETE/INCOMPLETE) with completion percentage, a commitment health score (HEALTHY/DRIFTING/OVERCOMMITTED), and a named next action.

📦 Add this skill to Claude Code

# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills

# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/productivity/weekly-review/skills/weekly-review .claude/skills/weekly-review

Skill source: productivity/weekly-review/skills/weekly-review/SKILL.md

⚠️ Good to know

Requires Python and a directory to scan; the skill relies on the user to provide honest input for the gate and auditor.

❓ FAQ

What happens if I skip a GET CURRENT step?

You can skip with a stated reason, but the gate will still name it and force an INCOMPLETE verdict if it's a mandatory step.

How long should a weekly review take?

Timebox it to 60-90 minutes; if it goes past two hours, gate what's done honestly and schedule the remainder.

Can I use this after a long break from reviews?

Yes, a lapsed habit restarts with a shorter pass and zero guilt — a review is maintenance, not judgment.

🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.