Claude Code skills, rules, and language bundles https://git.cjennings.net/rulesets/atom?h=main 2026-05-20T19:08:32+00:00 2026-05-20T19:08:32+00:00 Craig Jennings c@cjennings.net 2026-05-20T19:08:32+00:00 urn:sha1:e6b27ba85c0a5adc5925fc08165ce58beb4d8800 The spec recommended an Emacs keystroke mode (task-review.el). Implementation went the other way — a pure Claude workflow, no elisp — because the interactive mode would couple a rulesets-owned file to archsetup's init.el, and the daily Claude touchpoint already exists in daily-prep. I added a Revision section at the top recording the change: pure workflow, rulesets-owned, the task-review.org / open-tasks.org name swap, the staleness --list selection, and the startup nudge promoted to template-level. The elisp architecture and ERT sections stay as a record of the abandoned approach, flagged superseded. The todo task moves to DOING with per-component status: everything but the smoke test is done, and component 3 (the elisp) is dropped. 2026-05-16T16:59:40+00:00 Craig Jennings c@cjennings.net 2026-05-16T16:59:40+00:00 urn:sha1:daf960fad5169f0d3fa52bae770e83ad73344f30 docs/design/task-review.org captures the brainstorm output for a daily 5-min keystroke-driven review habit that walks 7 oldest-unreviewed top-level [#A]/[#B]/[#C] tasks per session, rotating through the list over ~12 days. Replaces wrap-it-up.org's date-coverage scan once implemented; the watchdog flips from "do all priorities have dates?" to "is the review habit happening?" with a 30-day threshold. todo.org gets a [#A] entry at the top of Rulesets Open Work pointing at the spec, so the implementation work isn't lost. Six components in the spec's Next Steps: extract task-review-staleness.sh, replace the wrap-up section, author task-review.el in archsetup, author the workflow file plus INDEX entry, add the startup nudge, smoke test.