Claude Prompt for Developer Work Log

Most developers only start a work log the week before a performance review and by then, three months of real work is already forgotten. The problem isn’t motivation, it’s format: a blank page asking “what did you do?” is hard to fill in well, especially for the kind of work that doesn’t show up in a commit history the Slack thread you unblocked someone on, the design doc you reviewed, the production issue you quietly prevented. This prompt is built to catch exactly that, by asking for it directly instead of leaving it to be remembered.

It’s built for software engineers, tech leads, and anyone who wants a real record of their work for daily standups, for the performance review they’ll thank themselves for later, or just to stop feeling like a week of real effort evaporated by Friday.

What makes it Work Perfectly:

  • It explicitly asks for “glue work” code reviews, mentoring, unblocking others, discussions as its own category, because that’s the work most likely to go unrecorded even though it’s often the most valuable
  • Each entry asks for impact, not just activity “fixed the auth bug” versus “fixed the auth bug that was causing 12% of login failures” are very different log entries, and only one of them is useful eight months from now
  • {raw_notes}, {time_period}, and {purpose} are separate variables, so the same messy notes produce a tight, scannable standup update or a fuller, narrative-driven perf-review entry depending on what you actually need that day

One honest note: this prompt organizes what you give it it can’t invent work you didn’t mention. See the Pro tips for the habit that makes it actually useful over time.