journal-thislisted

# journal-this ## What this skill does Turns the current conversation into a dated markdown journal entry — what got built, what broke, what got reshaped, what's deferred, and the cross-cutting lessons worth carrying forward — written in **the Operator's own voice** and saved to **the Operator's own journal** (a local folder or a GitHub repo). It is a generalized version of a personal journaling workflow. Before it can write anything for a new Operator, it runs a one-time **setup interview** to learn three things: who the Operator is, where their existing writing lives (so it can match their voice), and where new entries should go. After setup, invoking it just produces and files the entry. ## When to use vs. not **Use when:** - The Operator explicitly asks to journal the session (`/journal-this`, "journal this", "summarize what we did", "write this up as a journal entry"). - The Operator names their journal as the destination. - A substantial work session is winding down ("good stopping point", "let's call it here") — offer to journal it proactively; the entry is how context carries forward across machines and sessions. **Don't use when:** - The conversation just started and nothing substantive has happened — say so and skip rather than padding a thin session into a fake-substantial entry. - The Operator wants a quick chat summary, not a durable journal record. Confirm intent if ambiguous. ## First run: the setup interview **Trigger setup when** the config file (`~/.