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.
- License 许可
- MIT
- 所属仓库
- AlmogBaku/aos
- 最近更新
- 2026-11-15
- Stars
- ★ 5
- Forks
- 2
01 前言 Front Matter
- name
- schedule
- description
- 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.
03 SKILL.md 正文
schedule
Find real time for a commitment and write it down. This runs when the user speaks, not overnight — "I want to work on the CFP tomorrow" is worthless if the block appears at midnight.
1. Estimate
How long is this, honestly? Prefer the user's own number where they gave one; otherwise a rough estimate beats none, because it decides how much calendar to look for and lets the steward spot a two-minute job that has sat for three weeks.
Record it as estimate: on the action — 45m, 2h. Keep the granularity from onboarding;
invented precision (37m) reads as noise.
2. Read the calendar before proposing anything
Existing blocks, meetings, and the working windows from the global MOD.md. Then two rules
that come from the user, not from this skill:
- Working hours bound where a block may land at all.
- Sacred time is never scheduled over, and never silently moved. This skill writes to a real calendar, so that rule is what makes the capability trustworthy rather than something the user has to check up on. A conflict gets surfaced — "the only two-hour gap is during choir practice; shall I look at Friday instead?" — never resolved on their behalf.
The global MOD.md's red lines apply here too. Sending an invitation to another person is
acting outward as the user; blocking time on their own calendar is not.
3. Take the slot and write it
{{skill: capture}} hands you the page path. Reached directly ("find me two hours for the CFP"), find it first rather than guessing at the slug — the open set is small:
kb --base commitments find --where type=action --where status=next
kb --base commitments set actions/write-the-cfp.md block=2026-08-01T10:00 estimate=45m
kb set validates every key against the base's schema and makes its own attributed commit,
so nothing else is needed. Both fields are declared at install — an undeclared one exits 14
rather than writing a page lint would later flag.
Link the action to its project in the same pass where one exists. The outer quotes are
load-bearing — kb set runs each value through a YAML parser, so a bare [[…]] is read as
a nested list and stored as one, silently and with exit 0:
kb --base commitments set actions/write-the-cfp.md 'project="[[projects/booking-deal]]"'
That link is what lets the steward answer "what is this for" without reading the body — via
kb find --where 'project=[[projects/booking-deal]]', since kb links reads body text only
and never frontmatter.
4. Report the slot back
Name the actual time — "blocked 10:00–10:45 Saturday". A confirmation that does not say when is the one thing the user cannot verify at a glance.
Where this runs
Where the harness can spawn a sub-agent, run in one. Not for latency — taking ten seconds to find a good slot is fine, even reassuring — but because finding one means reading the calendar, the existing blocks and the project page, none of which the conversation needs in its context afterwards.
Inline is a correct fallback, not a failure. Say which one happened.
Without a calendar
Say so plainly, once: actions, statuses, deadlines and the steward all still work; there are
no blocks. Then set estimate: anyway and leave block absent — the steward's
--without block backstop is exactly the query that finds these, so a commitment with no
calendar is tracked rather than lost. Silently doing nothing is the one unacceptable
outcome, because the user believes time was found.
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).