weekly-review-planning — Claude Code skill: weekly reset and planning
weekly-review-planning — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that runs a structured weekly reset across tasks, calendar, and notes.
MIT 163 installs ★ 265,216 updated 2026-11-10
npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a claude-codeWhat weekly-review-planning does
The skill follows seven steps: confirm the timezone and review window, pull calendar data via google-workspace or another connector, process task inboxes and notes (obsidian, Notion, email-inbox-triage), reconcile active projects, surface commitments and waiting items, build a capacity-aware plan against real calendar load, then write only approved changes — reading each record back from the provider to confirm.
Output covers seven sections: completed commitments, overdue or at-risk items, waiting and follow-ups, stalled projects, next-week outcomes with calendar constraints, proposed updates pending approval, and coverage gaps. Nothing is mutated without explicit sign-off.
The skill expects you to declare an authoritative task store and resolve source-of-truth conflicts up front — it won't pick a winner automatically. It's separate from daily briefs and single-inbox triage, which belong to google-workspace and email-inbox-triage respectively.
What it helps with
- Find projects with no next action and propose a concrete step for each
- Collect all commitments from the past week and assign follow-up dates
- Match tasks and notes against real calendar capacity for the coming week
- Track waiting items and avoid treating silence from others as completion
- Schedule the weekly review as a cron job via the Automation Blueprint
Example prompts for the agent
- Run my weekly review for last week
- Which commitments are overdue or at risk right now?
- Build next week's plan from my calendar, tasks, and notes
How to install weekly-review-planning
1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a claude-code2Manually: put the files in place
~/.claude/skills/weekly-review-planning/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/weekly-review-planning/
1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a codex2Manually: put the files in place
.agents/skills/weekly-review-planning/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a cursor2Manually: put the files in place
.cursor/skills/weekly-review-planning/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NousResearch/hermes-agent skills/productivity/weekly-review-planning2Manually: put the files in place
.github/skills/weekly-review-planning/SKILL.md1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a gemini-cli2Platform CLI
gemini skills install https://github.com/NousResearch/hermes-agent --path skills/productivity/weekly-review-planningManually: put the files in place
.devin/skills/weekly-review-planning/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about weekly-review-planning
How do I install weekly-review-planning in Claude Code?
Run npx skills add NousResearch/hermes-agent --skill weekly-review-planning -a claude-code. The skill file is placed at ~/.claude/skills/weekly-review-planning/SKILL.md.
What does the weekly-review-planning skill do?
It runs a bounded weekly reset: reviews completed commitments, flags stalled projects and waiting items, then builds a capacity-aware plan for the next week. No tasks or calendar events are changed without your approval.
Does weekly-review-planning require Google Workspace?
The calendar step loads google-workspace or another declared connector — without one configured, that step won't run. The remaining steps for tasks, notes, and projects work with whichever sources you declared during setup.
Source text
SKILL.md · MIT
---
name: weekly-review-planning
description: "Weekly reset: commitments, stalled work, next-week plan."
version: 0.1.0
author: Ben Barclay (benbarclay), Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
hermes:
tags: [Weekly-Review, Planning, Tasks, Calendar, Productivity]
related_skills: [obsidian, google-workspace, email-inbox-triage]
---
# Weekly Review and Planning
Run a bounded weekly reset across the user's chosen systems. This is a concrete recurring task, not a generic productivity methodology — the `weekly-review` Automation Blueprint schedules it as a cron job.
## When to Use
- "Run my weekly review."
- "What did I commit to and what is slipping?"
- "Plan next week from my calendar, tasks, and notes."
- "Find stale projects and waiting items."
- A cron tick fires for a scheduled weekly review.
Don't use for: daily briefs (see the `google-workspace` daily-brief reference) or single-inbox triage (`email-inbox-triage`).
## Procedure
### 1. Set systems and window
Confirm timezone, review period, planning horizon, authoritative task/project store, calendars, inboxes, and allowed writes. Default to recommendations/drafts, not mutations. Done when source-of-truth conflicts have a declared winner.
### 2. Review calendar evidence
Load `google-workspace` or the relevant calendar connector. Inspect the completed week for meetings and commitments, then the next 1-2 weeks for deadlines, travel, preparation, and capacity. Capture follow-ups implied by past events and conflicts ahead. Done when both retrospective and horizon are covered.
### 3. Clear capture inboxes
Review the task inbox, notes (`obsidian`, Notion), flagged email (`email-inbox-triage` owns thread-level triage), and other declared capture points. Convert each item to next action, project, waiting, scheduled, someday, reference, archive, or delete proposal. Do not mutate until scope is approved. Done when remaining unprocessed items are counted and stated.
### 4. Reconcile active projects
For each project identify desired outcome, next action, owner, deadline, blocker, last meaningful activity, and source link. Flag projects with no next action, missed dates, duplicate records, or contradictory status. Done when every active project is actionable or explicitly paused.
### 5. Review waiting and commitments
Find promises made by the user and items owed by others. Propose follow-ups with dates and channels. Do not infer that silence means completion. Done when each waiting item has an owner and next review/follow-up date.
### 6. Build a capacity-aware plan
Estimate fixed calendar load and select a small set of weekly outcomes plus near-term next actions. Rank by consequence, deadline, dependency, and effort; do not fill every free hour. Done when the plan fits actual capacity and names deferred work.
### 7. Apply approved updates
Update tasks/projects, create calendar holds, archive processed items, and draft follow-ups only as approved. Read every changed record back from the provider. Done when verified writes match the review summary.
## Output Shape
1. Wins and completed commitments
2. Overdue or at risk
3. Waiting/follow-ups
4. Stalled or ambiguous projects
5. Next week's outcomes and calendar constraints
6. Proposed updates awaiting approval
7. Coverage gaps
## Pitfalls
- Planning from tasks without calendar capacity.
- Carrying every unfinished item forward as high priority.
- Marking projects active with no next action.
- Silently deleting or rescheduling personal commitments.
- Treating silence from others as completion.
## Verification
- [ ] Both the completed week and the planning horizon were covered, or gaps are stated.
- [ ] Every stalled/waiting flag traces to a specific record, event, or thread.
- [ ] No task, event, or note was mutated without approval; approved writes were read back.
- [ ] The plan names what was deferred, not just what was chosen.
© Ben Barclay (benbarclay), Hermes Agent · MIT · NousResearch/hermes-agent