agentleFS
blu3moblu3mo/gtd-cosense/skills/gtd-review/SKILL.md

gtd-review

Skill0 starsChanged 5 months agoMITView on GitHub

Guide a GTD review of the Cosense system so it stays trusted and current. Use for the Weekly Review (週次レビュー, 棚卸し, 見直し, "システム整える", "たまってきたから整理") or a quick daily check. Reads the whole system WITH UNDERSTANDING (including the user's casual hand-edits), empties 未処理, confirms every open loop has a live next action, sweeps Google Calendar for loose ends, and revisits someday. Part of the gtd skill bundle.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Ask 「頭に残ってて、まだ書けてないことある?」 → capture those first (gtd-capture).

    line 24
  2. Very specific:

    Every open loop has a live, still-valid next:: If a project's next action is done or stale, ask for the new one (set-fields --next).

    line 31
  3. Very specific:

    Calendar sweep (Google Calendar): use the connected Google Calendar MCP list_events (find via ToolSearch calendar if not loaded).

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

gtd-review — keep it clean, clear, current, complete

A GTD system only works if it's trusted, and it's only trusted if it's current. This ritual earns the mind's permission to let go the rest of the week. Do it with the user, as a conversation — read and understand their pages as they are (they hand-edit too); don't silently rewrite their system.

GTD=~/.claude/skills/gtd/scripts/gtd_cosense.py. Get oriented: python3 "$GTD" show (the panel, split into 📥未処理 / 🗂整理済み) and python3 "$GTD" waiting (待ち/waiting items, with overdue hints — advisory; you judge). Read the actual notes people left; they carry the state.

1. Get clear — empty 📥 未処理

Ask 「頭に残ってて、まだ書けてないことある?」 → capture those first (gtd-capture). Then run the gtd-clarify flow on everything in 未処理 until that zone is empty. Also read any free-form notes the user hand-added anywhere and fold them in (a scribbled "やっぱ急ぎ" is a real signal).

2. Get current — walk 🗂 整理済み

Item by item:

  • Every open loop has a live, still-valid next:. If a project's next action is done or stale, ask for the new one (set-fields --next). A project with no next action is the quiet thing that rots the system — fix it here.
  • Mark done items done: 「これ終わった?」→ complete --match … --commit (the page stays as record). Never move it back into the inbox.
  • Waiting-for: for each item from waiting, check the date; for old ones offer a graceful early nudge (「あの件、進んでますか」くらいの) rather than waiting for it to blow up. If it arrived, turn it into a next: or complete it.
  • Calendar sweep (Google Calendar): use the connected Google Calendar MCP list_events (find via ToolSearch calendar if not loaded). Look back over the recent past for loose ends (finished meetings/events whose follow-up isn't a next: yet — this often triggers 「あ、 そういえば…」) and forward over the coming week for anything needing prep now.
  • Stale check: anything untouched for a long time — still real? still yours? re-clarify, complete, or move-someday.

3. Get creative — someday & horizons

  • Re-read python3 "$GTD" show --page someday: promote anything ripe back to the inbox (capture + clarify it), delete what's genuinely dead. This periodic re-surfacing is the only thing that keeps someday/maybe worth having.
  • Optional light prompt (not every time): 「今の役割・関心で、まだ project になってないけど 気になってる領域ある?」 Anything real → capture → clarify.

Close by naming the finish line

「これで、やれることは全部見えてて、それぞれ次の一手が決まってる状態になった。」 That is a current, trusted system — the point of the ritual. Offer to make it a rhythm: 「毎週◯曜の この時間にやる?」 A weekly cadence is what keeps the mind willing to let go the other six days.

Quick daily variant

Compressed pass: new captures → clarify; scan 🗂 for today's live next:s and overdue waiting:; glance at today's Google Calendar; surface 1–3 things worth doing now (hand to gtd-engage).

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.