gtd-weekly-review: task new nachgezogen, veralteter Begründungszeiger korrigiert (#137)
CI / verify (push) Successful in 57s
Release / release (push) Successful in 35s

Files changed:
- CHANGES.md
- VERSION
- instructions/gtd-weekly-review/SKILL.md
This commit is contained in:
torben committed 2026-09-22 19:47:20 +02:00
1 parent 2cce979814
commit 8b535b4016
3 files changed
+31 -11

No files matched your search

+11 -9
View File
@@ -19,11 +19,12 @@ looked at yet.
API - only the tracker's generic role. That is deliberate: this skill is the one document that
must read identically in every instance, whichever tracker it runs against. Anything the tracker
itself must do - add a task, reschedule a reminder, remove an item - is described as an action the
user takes in their tracker, because `wikitool` has no command for it: the only two GTD commands
that exist are `review` (read-only) and `new project` (page + tracker project creation). That
narrow command surface is deliberate (see the reasoning in `types/project.md` and
`kb/gtd/COLLECTION.md`, which this skill does not repeat) - do not reach for a tracker-specific
tool or API to "just do it faster".
user takes in their tracker: a deliberate choice, not a gap in `wikitool`'s GTD command surface,
which also carries `task new` (tracker item only, no page) alongside `review` (read-only) and
`new project` (page + tracker project creation) - this skill simply does not call it. The
reasoning behind keeping the tracker and `kb/gtd/` on separate write paths lives in
`docs/knowledge-and-commitment.md`, which this skill does not repeat - do not reach for a
tracker-specific tool or API to "just do it faster".
## Steps
@@ -89,10 +90,11 @@ tool or API to "just do it faster".
`review`, `touch`, `new project`, `rename` (via `instructions/page-lifecycle.md`, only for the
rename case), `publish`
**Deliberately absent:** anything that reaches into the task tracker directly. `review` and
`new project` are the only two GTD commands this stack has (`types/project.md`); every other
tracker-side action in the table above - adding a next action, moving a reminder, removing an
item - is something the user does in their tracker, not something this skill automates.
**Deliberately absent:** anything that reaches into the task tracker directly. `wikitool`'s GTD
surface also includes `task new` (tracker item only, no page -
`docs/knowledge-and-commitment.md`), but this skill does not use it: every tracker-side action in
the table above - adding a next action, moving a reminder, removing an item - is something the
user does in their tracker, not something this skill automates.
## Output