diff options
| -rw-r--r-- | todo.org | 31 |
1 files changed, 26 insertions, 5 deletions
@@ -8,6 +8,9 @@ Project-scoped (not the global =~/sync/org/roam/inbox.org= list). * Rulesets Open Work ** DOING [#A] Implement task-review daily-habit per spec +:PROPERTIES: +:LAST_REVIEWED: 2026-05-20 +:END: Spec: [[file:docs/design/task-review.org]] Retires =wrap-it-up.org='s date-coverage scan and replaces it with a daily list-hygiene review (N=7 oldest-unreviewed top-level =[#A]= / =[#B]= / =[#C]= tasks per session, ~12-day rotation). Built as a pure Claude workflow — Shape B, no elisp; see the spec's Revision section for why the elisp approach was dropped. @@ -22,11 +25,17 @@ Status: Triggered by: 2026-05-16 brainstorm on retiring the date-coverage scan. -** TODO [#C] wrap-it-up Step 3.5 assumes GitHub-family remote :chore: +** TODO [#A] wrap-it-up Step 3.5 assumes GitHub-family remote :chore:quick: +:PROPERTIES: +:LAST_REVIEWED: 2026-05-20 +:END: Triggered by: 2026-05-16 wrap-it-up github.com cleanup (audit of the same file). Step 3.5 (Linear ticket-state hygiene) at =wrap-it-up.org:207= says "the project's GitHub remote — use =gh pr list ...=". Currently fine in practice: the step is Linear-gated, and the only Linear-using project is DeepSat (on =deepsat.ghe.com=, a GitHub-family host where =gh= works). Would break if a future Linear-using project lived on a non-GitHub host (gitlab, gitea, bitbucket). Either drop the GitHub-family assumption (provider-agnostic lookup, harder) or document the assumption explicitly so future projects know the step needs an update if they don't fit. ** DOING [#A] Check that memories are sync'd across machines via git.m +:PROPERTIES: +:LAST_REVIEWED: 2026-05-20 +:END: *** 2026-05-16 Sat @ 01:12:52 -0500 Spec #+begin_src cj: comment write the spec here. @@ -56,7 +65,10 @@ commit + push archsetup. After that, every machine running =stow= picks up the same memory tree. *** VERIFY Approve stow-based sync of ~/.claude/projects via archsetup/dotfiles/common/ -** TODO [#A] Build =create-documentation= skill for high-quality project/product docs +** TODO [#C] Build =create-documentation= skill for high-quality project/product docs +:PROPERTIES: +:LAST_REVIEWED: 2026-05-20 +:END: Create a Claude skill named =create-documentation= that can plan, write, refresh, and review software documentation across README files, project docs, @@ -690,7 +702,10 @@ The skill should reject: public/library/API docs: =llms.txt= or markdown export is valuable, but normal human navigation remains primary. -** TODO [#A] Review pass: tighten skills and rulesets after 2026-05-04 audit +** TODO [#C] Review pass: tighten skills and rulesets after 2026-05-04 audit +:PROPERTIES: +:LAST_REVIEWED: 2026-05-20 +:END: Source notes used in this pass: - C4 official docs: C4 is notation-independent; System Context and Container @@ -1219,7 +1234,10 @@ or compound commands, and can misidentify targets. Use =shlex= for simple commands, document unsupported shell constructs, and fail toward asking when a destructive pattern is ambiguous. -** TODO [#B] Build =ov-1= skill for DoDAF OV-1 (High-Level Operational Concept Graphic) +** CANCELLED [#B] Build =ov-1= skill for DoDAF OV-1 (High-Level Operational Concept Graphic) +CLOSED: [2026-05-20 Wed] + +Cancelled during the 2026-05-20 task review. Triggered by SOFWeek (May 2026, Tampa) — DeepSat attending; DoD attendees may ask for architecture diagrams. OV-1 is the universal informal @@ -1293,7 +1311,10 @@ See also the DoD-specific notations section under the later TODO starting point across the DoD notation landscape (SysML, DoDAF/UAF, IDEF1X). This entry is the execution plan for that starting point. -** TODO [#A] Build =/update-skills= skill for keeping forks in sync with upstream +** TODO [#C] Build =/update-skills= skill for keeping forks in sync with upstream +:PROPERTIES: +:LAST_REVIEWED: 2026-05-20 +:END: The rulesets repo has a growing set of forks (=arch-decide= from wshobson/agents, =playwright-js= from lackeyjb/playwright-skill, =playwright-py= |