torbenandClaude Opus 5.5
f9056c04f7
Files changed: - .gitea/workflows/ci.yml - .gitignore - .vibe/hooks.toml - AGENTS.md - CHANGES.md - EVALS.md - INSTALL-MCP.md - INSTALL.md - README.md - VERSION - docs/dev/development.md - docs/explanation/README.md - docs/explanation/architecture.md - docs/explanation/language-boundaries.md - docs/explanation/telemetry-and-evaluation.md - docs/how-to/README.md - docs/how-to/browse-with-obsidian.md - docs/how-to/capture-repository-docs.md - docs/how-to/export-guidelines.md - docs/how-to/ingest-a-source.md - docs/how-to/maintain-the-wiki.md - docs/how-to/query-the-wiki.md - docs/how-to/run-the-weekly-review.md - docs/how-to/set-up-the-mcp-server.md - docs/how-to/trace-and-score-sessions.md - docs/how-to/troubleshoot.md - docs/how-to/update-an-instance.md - docs/reference/README.md - docs/reference/commands/distribution-and-versioning.md - docs/reference/commands/instance-health.md - docs/reference/commands/raw-material-and-uploads.md - docs/reference/commands/telemetry.md - docs/reference/commands/types-instructions-and-docs.md - docs/reference/configuration.md - instructions/dev/dev-setup.md - instructions/dev/doc-pull-through.md - instructions/dev/stack-build/SKILL.md - instructions/dev/testing-conventions.md - instructions/dev/version-parts.md - instructions/setup-instance.md - instructions/upgrade-instance.md - reports/CONTRACT.md - tools/.coveragerc - tools/CONTRACT.md - tools/README.md - tools/chemenu/commands/dist_cmd.py - tools/chemenu/commands/docs_verify.py - tools/chemenu/commands/doctor.py - tools/chemenu/commands/eval_cmd.py - tools/chemenu/commands/git_publish.py - tools/chemenu/commands/upload_cmd.py - tools/chemenu/commands/version_cmd.py - tools/chemenu/evals/__init__.py - tools/chemenu/evals/scorecard.py - tools/chemenu/evals/trajectory.py - tools/chemenu/telemetry/policy.py - tools/chemenu/tests/test_dist_cmd.py - tools/chemenu/tests/test_git_publish.py - tools/chemenu/tests/test_instructions_shell.py - tools/chemenu/tests/test_pipeline_l0.py - tools/chemenu/toc.py Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
65 lines
3.2 KiB
Markdown
65 lines
3.2 KiB
Markdown
# Run the weekly review
|
|
|
|
Go through your committed initiatives once a week and decide what each one needs: a next action, a
|
|
pause, a close. A machine prepares the list, so you don't have to reconstruct it from memory. The
|
|
agent runs the `gtd-weekly-review` skill ([skill catalogue](../reference/skills.md)).
|
|
|
|
## Two places, on purpose
|
|
|
|
Knowledge and commitments change at different speeds, so they live in different places:
|
|
|
|
- **A page under `kb/gtd/`** is one initiative's durable memory: its goal, who is involved, where it
|
|
stands, and why it is worth doing. It never summarises the task list.
|
|
- **The open items** live in a task tracker, which owns them.
|
|
|
|
Nothing syncs between the two. `tools/wikitool review` joins them when it reads, matching on the
|
|
project name, and stores nothing - not even a report file. Why the split runs this way rather than
|
|
syncing: [knowledge-and-commitment.md](../explanation/knowledge-and-commitment.md).
|
|
|
|
## What you prepare
|
|
|
|
A task tracker, configured for this checkout in `.wikitool-tasks.json`. Super Productivity and
|
|
CalDAV (for example Nextcloud Tasks) are supported. The file's shape, and the difference between a
|
|
tracker the wiki can only read and one it can write to, is in the
|
|
[configuration reference](../reference/configuration.md#task-tracker). Without a tracker, the
|
|
review has nothing to join against. That is a valid state, though, and the pages work without one.
|
|
|
|
## What you say
|
|
|
|
```text
|
|
Run the weekly review
|
|
```
|
|
|
|
## What you get back
|
|
|
|
The agent runs `tools/wikitool review` and walks you through its findings, one at a time:
|
|
|
|
- initiatives with no next action;
|
|
- waiting-fors past their follow-up date;
|
|
- tracker projects that have no page;
|
|
- active pages with no open item;
|
|
- someday items that have gone stale.
|
|
|
|
For each finding, the agent asks what is actually true, because "this looks stalled" can mean a
|
|
next action is missing, the initiative was paused on purpose, or it is finished. Then it proposes the
|
|
exact change: a new item in the tracker, an item marked done, or a page's state moved to `dormant`,
|
|
`completed` or `abandoned`. Nothing is written to the tracker until you confirm that exact call.
|
|
What was decided goes onto the page, and the page is published.
|
|
|
|
A quiet week is a valid result. If one of the checks could not run because the tracker did not
|
|
answer, the agent says which check was skipped. An empty result under a skipped check means nothing.
|
|
|
|
## Starting something new
|
|
|
|
Ask the agent for a new project and name it. It runs `tools/wikitool new project`, which gives the
|
|
initiative its page under `kb/gtd/` and, where a tracker is configured, a tracker project under the
|
|
same name. A CalDAV tracker gets that project created automatically. On Super Productivity the
|
|
command stops with exit 42 and asks you to create the project in the app yourself. Tell the agent
|
|
when you are done, and it continues with `--resume`. A tracker the wiki can only read refuses the
|
|
command outright.
|
|
|
|
A single open item with no page of its own - a commitment that came with a source, say - is filed
|
|
with `tools/wikitool task new`. `task list` reads a project's open items back, and `task close --id`
|
|
marks one done. Nothing deletes an item. The commands are in the
|
|
[command reference](../reference/commands/pages.md).
|