alirezarezvani/claude-skills / productivity/weekly-review/skills/weekly-review
weekly-review
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| assets/example_weekly_review.md | markdown | 4.1 KB |
| assets/weekly_review_checklist.md | markdown | 2.4 KB |
| references/gtd_weekly_review_canon.md | markdown | 6.2 KB |
| references/open_loop_psychology.md | markdown | 6.0 KB |
| references/review_cadence_design.md | markdown | 6.2 KB |
| scripts/commitment_auditor.py | script | 7.3 KB |
| scripts/open_loop_scanner.py | script | 7.6 KB |
| scripts/weekly_review_gate.py | script | 9.2 KB |
assets/weekly_review_checklist.md
View on GitHub# Weekly Review Checklist
> Fillable template. Copy this file (or print it), work top to bottom, then gate it:
> `python scripts/weekly_review_gate.py --done "..." --skip "N:reason"`
**Week of:** ____________ **Started:** ____:____ **Timebox ends (max 2h):** ____:____
---
## Phase 1 — GET CLEAR
- [ ] **1. Collect loose inputs** — papers, receipts, notes, screenshots, downloads → into an inbox
- Scanner run? `python scripts/open_loop_scanner.py --dir ______ --stale-days 14`
- Loops found: checkboxes ____ · TODO/FIXME ____ · stale files ____
- [ ] **2. Process inboxes to zero** — clarify, don't do (two-minute rule is the only exception)
- Inboxes processed: ☐ email ☐ task inbox ☐ notes app ☐ desk/physical ☐ other: ______
- [ ] **3. Empty your head** — mind sweep; capture every commitment still riding in memory
- New items captured: ____
## Phase 2 — GET CURRENT (all five mandatory)
- [ ] **4. Review next-action lists** — mark done, prune dead, surface stuck
- Done: ____ · Pruned: ____ · Stuck (needs decision): ____
- [ ] **5. Review previous calendar** — missed or spawned commitments become captured items
- Items captured from the look-back: ____
- [ ] **6. Review upcoming calendar** — prepare, don't react
- Prep actions created: ____
- [ ] **7. Review waiting-for list** — chase, re-date, or drop each item
- Chased: ____ · Re-dated: ____ · Dropped: ____
- [ ] **8. Review project lists** — every active project has exactly one next action
- Auditor run? `python scripts/commitment_auditor.py --input ______`
- Health score: ____/100 · Verdict: ______
- STALLED: ____ · NO-NEXT-ACTION: ____ · SOMEDAY-CANDIDATE: ____
## Phase 3 — GET CREATIVE
- [ ] **9. Review someday/maybe** — activate, keep, or kill
- Activated: ____ · Killed: ____
- [ ] **10. Capture new ideas** — add them while the head is clear
- New ideas captured: ____
---
## Gate it
```bash
python scripts/weekly_review_gate.py --done "____________" --skip "____________"
```
**Gate verdict:** ☐ COMPLETE (exit 0) ☐ INCOMPLETE (exit 2)
**Missing steps named by the gate:** ______________________________________
## Close
**One next action for the coming week:** ______________________________________
**Finished:** ____:____ (total: ____ min — target 60-90)
> Skipped a step? Write the reason above and give it first priority next week.
> Lapsed last week? Shorter pass, zero guilt. The review is maintenance, not judgment.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |