wt-capture
Records something the user has said they must do themselves: classifies the commitment as next, waiting, someday or trivial, writes it as an action page in their commitments base, and hands off to wt-schedule when it needs real hours. Use when the user commits to work of their own — "I need to find time to…", "I have to…", "remind me to…", "help me remember…", "put that on my list", "I should … at some point". Do NOT use when the user asks the assistant to do the work ("write the CFP", "research X", "email Sam") — that is a request to act now, not a commitment to track. Do NOT use for thoughts, facts or notes carrying no commitment; those are knowledge and belong to kb-capture.
- License 许可
- MIT
- 所属仓库
- AlmogBaku/aos
- 最近更新
- 2026-11-15
- Stars
- ★ 5
- Forks
- 2
01 前言 Front Matter
- name
- wt-capture
- metadata
- { "aos": { "origin": "work-tracker@0.1.5" } }
- description
- Records something the user has said they must do themselves: classifies the commitment as next, waiting, someday or trivial, writes it as an action page in their commitments base, and hands off to wt-schedule when it needs real hours. Use when the user commits to work of their own — "I need to find time to…", "I have to…", "remind me to…", "help me remember…", "put that on my list", "I should … at some point". Do NOT use when the user asks the assistant to do the work ("write the CFP", "research X", "email Sam") — that is a request to act now, not a commitment to track. Do NOT use for thoughts, facts or notes carrying no commitment; those are knowledge and belong to kb-capture.
03 SKILL.md 正文
capture
Write the page, confirm, hand off. Under five seconds to the confirmation.
Clarify — one question, asked of yourself
Is this mine to do? Not "is it actionable?" — everything is actionable to an agent, so that question routes every request into the list.
| The commitment is | status: | plus | then |
|---|---|---|---|
| real work of the user's | next |
— | hand off to wt-schedule |
| someone else's to answer | waiting |
waiting_on: |
nothing more |
| a deadline, not hours | next |
due: |
a reminder, no block |
| not now, maybe never | someday |
— | nothing more |
| trivial | next |
estimate: |
say "that's a two-minute job — worth doing now?" and file it anyway |
status is one of exactly those four words. Nothing validates it, so a fifth value —
trivial, blocked, urgent — is written happily and then matches none of the steward's
queries nor its --without block backstop, which makes the commitment permanently invisible.
Trivial work is next with a small estimate:, not a status of its own.
someday protects the list: without it every musing becomes a scheduled commitment, and a
schedule the user stops trusting is worse than none.
Never block on the recommendation. Ask about the two-minute job in the same breath as
confirming, not instead of it — a commitment lost to a clarifying question costs more than a
wrong estimate. If the exchange resolves it ("yeah, done"), file it done with an
expires: rather than skipping the page.
Write it
The page is actions/<slug>.md, and there is no kb verb that creates one — write it with
ordinary file tools, then attribute it:
kb --base commitments commit --verb create --path actions/write-the-cfp.md \
--summary "commitment: write the KubeCon CFP"
All three flags are required. Skip this and the page reaches git only through the sync sweep,
with no acting subject, and kb lint reports it — as a report, not a failure: bare kb lint
exits 0 even with criticals in it, so read what it says rather than trusting the exit code.
Frontmatter. The four marked required are the ones kb lint reports as missing — write all
seven anyway, since the steward's queries depend on status and since:
title: call the dentist # required
type: action # required
created: <DATE> # required
timestamp: <TIMESTAMP> # required
status: next # plus due / estimate / waiting_on per the table above
since: <DATE>
slipped: 0
The user's own words go in the body, verbatim — that sentence is the only record of what they actually committed to, and a tidier paraphrase is usually a paraphrase of what you assumed they meant.
Then add the page to index.md, or it is invisible to the map even though every query still
finds it: kb --base commitments index rebuild does it mechanically.
Shape and the full field list: the work-tracker skill's reference/action-page.md.
A correction to something already filed is kb capture --corrects <path> — a link, not prose
for a later pass to guess at.
Hand off
Needs real hours → invoke wt-schedule, in a sub-agent where the harness has them and inline
otherwise. Which one happened, and whether a block was taken or there was no calendar, is
recorded on the page (block present or absent) rather than said: this user's confirmation
is the 🦜 alone, and an unblocked commitment surfaces in the steward's nightly backstop count.
The user should experience one act, not two. wt-schedule comes back with the time; you confirm once — and per the user's preference below, that one confirmation is the 🦜.
How the confirmation reads is the user's call: confirm every commitment with a single 🦜 emoji — nothing else, ever. Never echo the commitment back, not even after wt-schedule took a block: the confirmation is still just 🦜 (the time is on their calendar and on the page, and they can ask). A sacred-time conflict wt-schedule surfaces is a question, not a confirmation, and still gets asked. Honour it exactly — this is the line they see several times a day, and it is the whole surface of an interaction whose other half is silent.
How the page is phrased is verb-first — "Email Sam the deck", not "Sam has the deck" —
in the title:. Anything with a deadline gets the deadline in the title too ("Submit the
KubeCon CFP by Fri 21 Nov"), because that is the part worth seeing at a glance. The body
still holds the user's own words verbatim.
When something fails
The commitment matters more than the bookkeeping around it. If the page landed and the
attribution, the flag or the hand-off did not, mention it and move on — an unscheduled action
is one without a block, which the steward's --without block backstop already finds. Losing
the thought is the only real failure here.
04 同仓库更多 Skills
wt-update
Updates an existing commitment when the user reports progress: completion, a new deadline, a stall, or abandonment. Use when the user says "I did that", "finished X", "still waiting on Y", "push that to next week", "I started it", or "forget it, I'm not doing X". Finds the matching open action, applies the change, and routes any knowledge the report carries to the knowledge base. Do NOT use to file a new commitment (that is wt-capture) or to find time for one (wt-schedule).
wt-steward
Maintains an existing commitments backlog: overdue, about to expire, stalled, and repeatedly-rescheduled commitments, and someday items gone cold. Use when the nightly cron job fires or the user asks to review or tidy their backlog ('review my backlog', 'what's gone stale on my list'). Does not capture or schedule new work — that happens when the user speaks, through wt-capture and wt-schedule.
wt-schedule
Estimates a commitment, links it to its project, and blocks time for it on the user's calendar. Use when the user asks to find time for something — "when can I do this?", "find me two hours for the CFP", "block time for that tomorrow", "I want to work on it today" — and immediately after wt-capture files a commitment that needs real hours. Do NOT use for a commitment that needs only a deadline or a reminder, and do NOT use to change what the user committed to — that is wt-update.
wt-capture
Records something the user has said they must do themselves: classifies the commitment as next, waiting, someday or trivial, writes it as an action page in their commitments base, and hands off to wt-schedule when it needs real hours. Use when the user commits to work of their own — "I need to find time to…", "I have to…", "remind me to…", "help me remember…", "put that on my list", "I should … at some point". Do NOT use when the user asks the assistant to do the work ("write the CFP", "research X", "email Sam") — that is a request to act now, not a commitment to track. Do NOT use for thoughts, facts or notes carrying no commitment; those are knowledge and belong to kb-capture.
work-tracker
Answers questions about the user's own commitments by querying their commitments base, explains the four statuses (next, waiting, someday, done), routes a request to the right work-tracker skill, and states who may change what without asking. Use when the user asks what they should be working on, what is overdue, what they are waiting on, or how their task tracking works, and no narrower work-tracker skill matches. Do NOT use to file a commitment the user just made (that is wt-capture), to find time for one (wt-schedule), or to report progress on one (wt-update).
kb
Explains how the user's knowledge bases are laid out and which kb skill handles a given job — the tree, the one queue, expiry, links, base health, maintenance. Use when the user asks how their knowledge base works, what state a base is in, why something was or was not kept, or wants base maintenance run, and no narrower kb skill matches. Do NOT use to file something the user just said (that is kb-capture), to answer a question from stored knowledge (that is kb-recall), or to pick a destination base for a write already in hand (that is kb-route).