Fold /weekly's load-bearing checks into nightly /daily; retire the weekly cadence
Highlight text on any card (body, plan, or an event) to anchor a comment, or leave a whole-task comment here. Mention @claude to summon a reply.
No comments yet.
Overview / Motivation
/weekly is not automated (never cron-run; its Friday nudge was disabled
2026-06-17) and has run exactly once (logs/weekly/2026-W22.md, May 31). Its
load-bearing functions have been rotting for ~4 weeks. Every consolidation
function /weekly performs is a CHECK that is strictly better run nightly
(catch drift in 1 day, not 7) — there is no cost or statefulness reason for a
separate weekly cadence. The user directive: "could weekly stuff not just be
daily? Basically I just want all of this automated so I don't have to run it."
Goal
Fold /weekly's load-bearing checks into the reliable nightly run and retire
the separate /weekly cron cadence, so nothing load-bearing depends on a
weekly skill the user never runs.
Scope / surfaces
- Fold into the nightly run (the LLM
/dailyjudgment pass and/or the deterministic consolidator, whichever fits each check):docs/open_questions.mddrift check — the periodic "should this question be reworded / split / settled / retired" pass. Per-issueliving-docs-updateris accretive only; this higher-level drift pass has no other home. Run nightly, idempotent (do not re-propose an open proposal).- Parked/declined-proposal backstop (
workflow.yaml:560,:2032— "parks for a future/weeklybackstop" / "future backstop re-synthesis (/weekly)") — re-consider declined/parked proposals nightly.
.claude/skills/weekly/SKILL.md— re-document/weeklyas a MANUAL-only on-demand deep-dive (no cron); state that nothing load-bearing depends on it..claude/workflow.yaml:560+:2032— repoint the backstop references to the nightly run..claude/agents/research-pm.md+.claude/skills/pm/SKILL.md— update the Wednesday/weeklysuggestion: mentor-meeting prep (the one genuinely weekly rhythm) stays as a manual//mentor-update-slidessuggestion, but the consolidation responsibilities move to nightly.
Constraints / invariants
- Workflow-surface only.
docs/open_questions.mdmutations stay USER-GATED (theliving_docs_updategate is user-only) — the nightly drift check PROPOSES, never applies.- Idempotent: nightly re-runs must not spam duplicate proposals for the same drift / parked proposal.
scripts/workflow_lint.py+ ruff pass; keepworkflow.yaml,CLAUDE.md, and the rule/skill files consistent.
Acceptance
docs/open_questions.mddrift and parked-proposal re-consideration run as part of the nightly automation;logs/weekly/no longer needs a nightly producer./weeklyskill carries a clear "manual deep-dive only; nothing depends on this running" banner.- A second nightly run does not re-propose a drift edit already proposed and still open.