Personal close-day skill checks today's dated tasks against Linear¶
- Date: 2026-11-06
- Status: Accepted
- Tags:
toolingworkflow
Context¶
On the personal Mac, a task in the daily note with a 📅 date means "start this today". Larvis turns each dated, project-tagged task into a Linear issue (PHA-222), and agents may move issues to In Progress (ADR 0041). Nothing checked, at the end of the day, that the work actually started, so a broken link in the chain (an unknown tag, an issue left in Todo, a Linear/Obsidian mismatch) went unseen.
The work laptop's close-day (in the synced harness, claude/harness/skills/close-day)
does something different: per-session handoff, ticket proposals and a panel index.
Decision¶
A personal skill, claude/skills/close-day, installed with
just install-personal-claude-skills. It runs larvis tasks check (read-only, one Linear
request) and walks the user through each ✗ and ⚠, offering fixes but changing nothing
without being told. The check's logic lives in Larvis, not the skill, so the morning briefing
can rerun it for yesterday.
Alternatives Considered¶
| Option | Why Rejected |
|---|---|
Adapt the work harness close-day |
Generated mirror of the work laptop (ADR 0033); its steps are about work tickets and panels |
| Put the checking logic in the skill | An LLM judging pass/fail is not deterministic, and the briefing couldn't reuse it |
| A scheduled job that notifies at night | A miss needs a decision (start it, retag, re-date), which is a conversation; the briefing covers skipped days |
Consequences¶
Positive:
- Every dated task gets a verdict at the end of its day, with the fix named.
- Read-only by default; closing issues stays human.
Negative / Trade-offs:
- Two skills named
close-dayexist, one per machine; the harness sync keeps them apart.
Ongoing obligations:
- Run it before
obsidian-todo-reschedule, which would otherwise hide the misses.
ADRs are immutable. If this decision changes, create a new ADR with status "Superseded by" pointing here, and update this record's status.