devloglisted

# Devlog ## Overview Devlog is continuous, point-in-time work commentary: what happened, why, and anything surprising, captured as it happens instead of reconstructed from memory at the end of a session. One narrative session note accumulates every entry from the current session — no separate "learnings" system, no til/cursed split, everything worth remembering goes in the same place. Processing (routing, connecting, daily-linking) happens later via `/second-brain:process-inbox`. This skill only ever appends to the inbox. **Write the entry now, in the same turn as whatever triggered it.** Don't ask "should I log this?" and don't offer to — just write it. Asking is exactly the failure mode that made the old `distill-conversation` flow get skipped: by the time a session ends, you're mentally done, and a skip-able step gets skipped. ## When to write - Finished a feature or fixed a notable bug - Wrapping up a work session - Discovered something non-obvious: a gotcha, undocumented behavior, a workaround that took several tries, a constraint you only noticed after hitting it ## When not to write - Routing, connecting, or moving existing notes — that's `/second-brain:process-inbox` - Reading an external source and writing it up — that's `second-brain:capture` - Trivially obvious or one-off details you'd never reach for again - Project-specific context (a config value, a repo convention) — that belongs in Claude Code's own memory system, not the vault ## Step 1: Lo