progloglisted

# Prog-log entry <!-- Published version: the source skill targets a specific file in the user's private strategy repo. The mechanism (dated first-person journal, concept-recall section, session-start staleness check) is the pattern worth reusing; the destination path is genericized below — swap in your own private journal location. --> `<your-private-notes-repo>/prog-log.md` is a private, dated pair-programming journal — what the user relearned each session (moving from one stack to another, strong on fundamentals, rusty on syntax — this is the relearning bridge toward a target role) and what he was building. It's written in **his** voice, first person, assisted-by Claude — not a third-person summary of him. He's said outright he won't reliably remember to trigger this himself, so this skill carries both ends: offering to log at session end, and catching a missed log at the next session's start. ## Entry format (match the existing file, don't improvise a new shape) Read `<your-private-notes-repo>/prog-log.md` before drafting — it already has real entries to pattern-match against. The established shape: - Header line: `## YYYY-MM-DD — <short title>` - Body as short paragraphs, each led by an inline bold label (not a markdown subheading): `**Working on:**`, `**What I built (hands-on pairing):**`, `**Process notes:**` / `**Process lessons:**`, `**Up next:**` — used flexibly, skip ones with nothing to say. - `**Concepts that came back to me:**` as its own