diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-15 15:05:37 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-15 15:05:37 -0500 |
| commit | 421b17a15219c7061ee92c07451993965fad88ea (patch) | |
| tree | 20cb0fe6f7bfc7ad2c4b0d46d93ccf8d5551728f /scripts | |
| parent | 7dd10e23cc78fab028b9ad27f0aaca0b8ec783c9 (diff) | |
| download | rulesets-421b17a15219c7061ee92c07451993965fad88ea.tar.gz rulesets-421b17a15219c7061ee92c07451993965fad88ea.zip | |
docs: codify depth-based completion rule + DRY the skill reference
Todo-format.md gets a "Completion — depth-based" section that
codifies what was implicit before: top-level (* and **) DONE tasks
stay task-shaped (DONE + CLOSED line), sub-tasks (*** and deeper)
flip to dated event-log entries, and VERIFY is the documented
exception (always dated-rewrite regardless of depth). The section
includes worked examples and the rationale for depth-based over
keyword-based.
The cj-comments skill's completion section now references the
canonical rule instead of restating the depth-based rules inline.
The three-bullet recap in the skill stays as a quick scan, but the
details and examples live in one place.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions