daily-journal

1# Daily Journal
2 
3## Purpose
4Keep an **automatic, passive** journal of your workdays so you don't have to write one. Claude logs what got done as it happens; you optionally run a reflection later. This is distinct from `/weekly-checkin` (which is a manual reflection where you supply the input) — here **Claude is the author** and the log accrues in the background.
5 
6Two modes:
71. **`log`** (default, mostly invoked implicitly) — append a short entry to today's journal.
82. **`reflect`** — read the day's log (+ recent days) and run a guided reflection with you.
9 
10## Storage
11- One file per day: `01-daily/journal/YYYY-MM-DD.md` (use `date +%F` for today's date; never guess).
12- Create the file from the template below on the first entry of the day.
13- Append only — never rewrite earlier entries. Newest entries go at the bottom of the Log section.
14 
15## When to log (procedure for the always-apply trigger)
16The trigger itself lives in `CLAUDE.md` § Daily Journal (ALWAYS APPLY), because a skill body is lazily loaded and cannot fire itself. This section is the procedure that trigger runs.
17 
18After finishing a **meaningful** unit of work, append one entry. Meaningful = would matter to future-you or shows how the day was spent. Examples:
19- Shipped/committed something, published a note/brief/slide, filed or moved tracker issues (Linear/Jira/GitHub).
20- Made a decision, changed direction, or hit a notable blocker.
21- Produced a deliverable file (spec, plan, analysis, report).
22…