agentleFS
Sign inStart free
minosinminosin/gtdbrain-claude-plugin/skills/weekly-review/SKILL.md

weekly-review

Skill0 starsChanged 38 days agoMITView on GitHub

Plan the user's week with a GTD weekly review of their GTD Brain board. Use when they say "plan my week", "weekly review", "help me get organised", "I feel behind", or want their whole to-do list, projects and follow-ups up to date.

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quarterly-review, daily-plan and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Phoenixrr2113Skill

    quarterly-review

    Quarterly review — strategic look at the last 3 months. Career trajectory, project health, life balance, big decisions ahead. Runs 1st of Jan/Apr/Jul/Oct.

    Also in 3 projects that use this

  • steptianSkill

    daily-plan

    每日待办计划与日程管理。触发词：'今天要做'、'今日计划'、'今日待办'、'今天安排'、'安排一下'、'加个任务'、'记个任务'、'今日复盘'、'今日回顾'、'今天总结'、'本周计划'、'周总结'、'开始工作'、'上班了'、'完成了'、'加个日程'、'记个日程'、'改一下时间'、'日程调整'、'面试'、'开会'、'约了'。支持四象限优先级、时段分配、固定日程管理、智能时间估算、每日/每周复盘。当用户提到有明确时间的安排（如'下午两点面试'、'10点开会'），自动识别为日程并写入日程表。

    Also in 3 projects that use this

  • seedprodSkill

    daily-brief

    Send a morning briefing via Telegram with weather, news, and a motivational quote. Designed to run via launchd for automated daily delivery.

    Also in 5 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 8 projects that use this

  • Phoenixrr2113Skill

    morning-brief

    Full morning brief — calendar, email, meeting prep, execute actionable items, create follow-up tasks. Runs at 8:03 AM or when Randy asks for a morning update.

    Also in 4 projects that use this

  • zephyrwang6Skill

    daily-review

    每日工作回顾与洞察分析，对用户前一天的对话历史和使用数据进行总结与建议

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the user's GTD weekly review, reading every list with a tool and never from memory.

    line 6
  2. Very specific:

    If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

    line 8
  3. Very specific:

    Phase 1 — Get Clear: Call list_columns, then list_cards for the Inbox, and clarify each card: a next action (move_card to Next Actions, …

    line 10
  4. Very specific:

    Phase 2 — Get Current: Call list_projects and list_next_actions.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 79 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the user's GTD weekly review, reading every list with a tool and never from memory. Go one list at a time and wait for the user's answers. If no GTD Brain tool is available, follow /gtdbrain:setup instead of guessing.

Phase 1 — Get Clear. Call list_columns, then list_cards for the Inbox, and clarify each card: a next action (move_card to Next Actions, update_card with a context), a project plus its first next action (create_card for each), a Waiting For card (move_card, then update_card with who and since), a Someday/Maybe card (move_card), or archive_card.

Phase 2 — Get Current. Call list_projects and list_next_actions. For each project ask "Is this still moving, and is its next action right?" and flag any project with no next action so you define one together with create_card. Then call list_waiting_for and for each card ask "Still waiting? Follow up if it has gone stale."

Phase 3 — Get Creative. list_cards for Someday/Maybe and ask for each: activate it (move_card to Next Actions or Projects), keep incubating, or let it go (archive_card).

End with a short summary of what changed and one concrete next step.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free