<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/.ai/workflows/open-tasks.org, branch main</title>
<subtitle>Claude Code skills, rules, and language bundles
</subtitle>
<id>https://git.cjennings.net/rulesets/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/rulesets/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/'/>
<updated>2026-05-28T14:08:43+00:00</updated>
<entry>
<title>feat(open-tasks): archive-done sweep at start of Phase A</title>
<updated>2026-05-28T14:08:43+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-28T14:08:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=beb646e827802c0491b422ce03c7687eb66a717b'/>
<id>urn:sha1:beb646e827802c0491b422ce03c7687eb66a717b</id>
<content type='text'>
open-tasks.org Phase A now runs `emacs --batch -q -l
.ai/scripts/todo-cleanup.el --archive-done todo.org` as a pre-step
before the parallel read batch. A level-2 task that completed during
the session sits as ** DONE under Open Work until something archives
it, which means Next Mode would surface it as a "what's next" candidate
between cleanups. The pre-step ensures Phase A's read of todo.org
reflects current state.

The pre-step skips only in an explicit read-only or dry-run context.
Default is always to sweep.

Common Mistake #13 records "recommending a freshly-DONE task" with the
pointer back to the pre-step.

The proposal came from a pearl handoff on 2026-05-28.
</content>
</entry>
<entry>
<title>feat(workflows): audit-warranted pre-step + priority and tag enforcement</title>
<updated>2026-05-28T13:08:20+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-28T13:08:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=ee7049aaa62d0c38e83f20c0b3796e5eded4ca23'/>
<id>urn:sha1:ee7049aaa62d0c38e83f20c0b3796e5eded4ca23</id>
<content type='text'>
Two changes land together because each is broken without the other.

open-tasks.org gains a new Phase A.1, evaluated only in Next Mode. The
phase reads :LAST_AUDIT: from notes.org and walks five state signals
(reminder/task mismatch, passed scheduled date, "waiting on X" matches a
shipped X, dead file: link, sub-task &gt;75% DONE coverage). If the temporal
threshold of 14 days trips, or any signal fires, Next Mode offers a
task-audit run before producing the recommendation. Item 1 in the offer
is "run task-audit first" per the recommendation-at-item-1 convention.

task-audit.org gains two pieces. Phase C now enforces priority and
type-tag presence per the project's legend, applies the [#A] dating rule
from that legend, and re-assesses :quick: and :solo: from reconciled
facts. Unambiguous calls land autonomously. Ambiguous ones flag
NEEDS-USER instead of being guessed. A new Phase E stamps :LAST_AUDIT:
on completion.
</content>
</entry>
<entry>
<title>refactor(workflows): rename task-review.org to open-tasks.org</title>
<updated>2026-05-20T18:58:01+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-20T18:58:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=49898a8c364430abf792567d2a51ac09db97a94f'/>
<id>urn:sha1:49898a8c364430abf792567d2a51ac09db97a94f</id>
<content type='text'>
The list-and-pick-next workflow was named task-review.org, but "task review" better describes a list-hygiene habit that re-grades and prunes tasks, not one that just displays them. I'm freeing the task-review.org name (and the "task review" trigger) for that habit, which lands next.

This workflow goes back to open-tasks.org — the name it carried before it merged with whats-next.org. Its content and INDEX entry drop the "task review" trigger and point at task-review.org for the hygiene habit. Behavior is unchanged; only the name and the routing phrases move.

The rename touches both the canonical workflow and the project mirror.
</content>
</entry>
</feed>
