agentleFS
ohanyanohanyan/adulting/skills/weekly-review/SKILL.md

weekly-review

Skill1 starsChanged 7 months agoMITView on GitHub

The canonical weekly review. GTD capture/clarify + Covey roles and goals + Ryan Holiday virtue audit. 45 to 90 minutes, usually Friday afternoon or Sunday evening. Phone in another room.

99 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 10 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

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user says they don't have the time, ask: "What would you be doing instead that is more important than deciding what next week is …

    line 17
  2. Distinctive:

    If it takes under 2 minutes, do it now.

    line 38
  3. Distinctive:

    If you do not put these in first, they will not happen.

    line 80
  4. Very specific:

    Write ~/adulting-data/journal/weekly-review-YYYY-MM-DD.md with all sections above.

    line 102
  5. Very specific:

    Ask the user: "Any of these you want help drafting or scheduling?" Offer to dispatch /partner-checkin, /hard-conversation, or /repair as …

    line 109

“Common” is measured: kept by at least 6 in 10 of the 85 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

/weekly-review

The single highest-leverage hour of the week. Skip it and the system breaks in about three weeks.

Setup

  • Phone in another room.
  • 60 to 90 minutes blocked.
  • Cup of coffee or tea.
  • ~/adulting-data/journal/weekly-review-YYYY-MM-DD.md open.

If the user says they don't have the time, ask: "What would you be doing instead that is more important than deciding what next week is for?"

Phase 1: Clear (15 minutes)

Empty every inbox:

  1. Email inboxes (all of them).
  2. Notes app, Apple Notes, random text files.
  3. Voice memos.
  4. Physical papers on desk.
  5. Browser tabs.
  6. The back of your mind. Ask: "What have you been carrying that you have not written down?"

Everything becomes one of:

  • Next action (a physical thing you can do).
  • Project (anything that takes more than one action).
  • Waiting-for (you owe nothing, someone else owes you something; track it).
  • Someday (not now, not dead).
  • Reference (file it).
  • Trash.

If it takes under 2 minutes, do it now.

Phase 2: Reflect (15 minutes)

Scan last week's calendar. For each day ask silently:

  • Did I spend the day on what I said mattered?
  • Where did my time actually go?

Then answer, in writing:

  1. Three wins this week. Be specific.
  2. Three misses this week. Be honest. No rationalization.
  3. Three lessons. What did I learn about the work, about people, about myself?
  4. What did I avoid this week? (The avoided thing is often the most important thing.)

Phase 3: Roles and goals (Covey, 15 minutes)

List your roles. A typical list:

  • Self (health, learning, soul)
  • Partner
  • Parent (one line per kid)
  • Son / daughter (parents)
  • Brother / sister / friend
  • Professional role 1 (e.g., CEO of X)
  • Professional role 2 (if applicable)
  • Citizen / community

For each role, ask: "What is the one thing I could do in the next 7 days that would move this forward?"

This is where most people drop the plot. The CEO who has no goal for "partner" or "son" this week is the CEO who will wake up in 10 years shocked.

Phase 4: Big rocks (10 minutes)

Open next week's calendar. Before meetings and work tasks fill it, schedule:

  • Training blocks (see /training-plan).
  • Deep work blocks (one per day, minimum 90 minutes).
  • Partner check-in (see /partner-checkin).
  • 1:1 time per kid (see /kid-oneonone).
  • Weekly review for next week.
  • Any tired-future-self favors (gym bag prepped, meals prepped).

If you do not put these in first, they will not happen. The calendar is the truth, the to-do list is a wish.

Phase 5: Virtue audit (5 minutes)

From Ryan Holiday's cardinal virtues:

  • Courage: where did I avoid this week? what hard conversation am I postponing?
  • Discipline: where did I let a standard slip?
  • Justice: who did I fail, and what is the repair?
  • Wisdom: what did I see more clearly this week? what am I still wrong about?

Phase 6: The four killer questions

End with these. One sentence each:

  1. What am I avoiding?
  2. What is the one week-making task?
  3. Who needs a message from me?
  4. What would make next week a 10 out of 10?

Output

Write ~/adulting-data/journal/weekly-review-YYYY-MM-DD.md with all sections above. Then print back:

  • The top 3 outcomes for next week.
  • The week-making task.
  • Any calendar holds to book now.
  • Any repairs owed.

Ask the user: "Any of these you want help drafting or scheduling?" Offer to dispatch /partner-checkin, /hard-conversation, or /repair as follow-ons.

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.