What if I genuinely didn’t do much glue work this period?

Skip the section rather than padding it the prompt is instructed not to invent impact that wasn’t in your notes, so an honest “nothing significant this week” is better than a stretched entry.

Can I use this for a team’s work log, not just my own?

It’s written for individual logs, but you can adapt it by replacing {raw_notes} with a summary of the team’s updates just expect the “impact” framing to need more context since it’s covering multiple people’s work.

03 views

Claude Prompt for Developer Work Log

Turns messy daily notes, commit messages, and Slack updates into a structured work log key work, impact, blockers, and the “glue work” that’s easiest to forget built for standups and performance review season alike.

Updated on October 12, 2026· By Kamran Kazmi

Last tested October 12, 2026 against Claude

The Prompt

Act as an engineer helping a colleague turn raw notes into a clean, structured work log entry. The raw notes are: "{raw_notes}". The time period this covers is "{time_period}". This log is being written for:...

CategoryCoding

Perfect forDeveloper Work Log

Recommended models

Claude

Variables

Placeholder{Raw_notes}

Examplefixed the race condition in the payment webhook (was causing ~5% of duplicate charges), reviewed Sarah's PR for the new rate limiter, helped onboard the new hire on our deploy process, still waiting on infra team for staging access

What to change it toWhatever messy notes you have commit messages, Slack recaps, a mental list the less polished, the better the prompt's structuring actually helps.

Placeholder{time_period}

Examplethis week (Oct 6-10)

What to change it toWhat the log entry covers shapes whether it reads as a single day or a longer stretch.

Placeholder{purpose}

Examplestandup

What to change it toWhat the log is for "standup" keeps it tight and present-tense; "brag document" or "performance review" writes fuller entries with stated impact.

Placeholder	Example	What to change it to
{Raw_notes}	fixed the race condition in the payment webhook (was causing ~5% of duplicate charges), reviewed Sarah's PR for the new rate limiter, helped onboard the new hire on our deploy process, still waiting on infra team for staging access	Whatever messy notes you have commit messages, Slack recaps, a mental list the less polished, the better the prompt's structuring actually helps.
{time_period}	this week (Oct 6-10)	What the log entry covers shapes whether it reads as a single day or a longer stretch.
{purpose}	standup	What the log is for "standup" keeps it tight and present-tense; "brag document" or "performance review" writes fuller entries with stated impact.

Actual output, by model

Real output this exact prompt produced — not a description of what it might do.

Claude

Standup format output as logged above, verbatim.

Which model runs this best

Claude correctly applied the standup-format branching rule tight, terse bullets with no invented impact narrative and included only details actually present in the notes, including the real ~5% duplicate-charge figure rather than fabricating one. It did show a minor tense inconsistency (mixing past and present tense across bullets) and flattened the four named sections into one undifferentiated list, which a careful user might want to adjust depending on how literally they want the structure preserved.

Turns messy notes, commit messages, or Slack recaps into a structured log entry key work with impact, glue work, blockers, and what’s next formatted for either a quick standup or a fuller record.

How To Use

Replace {raw_notes} with whatever you’ve got bullet points, commit messages, a Slack message you wrote to someone, doesn’t need to be clean
Replace {time_period} with what it covers (e.g. “this week,” “October 6-10”)
Replace {purpose} with “standup,” “brag document,” “performance review,” or leave it out for a general log entry
Paste into Claude

1.Log on a cadence, not just before a review even a rough 10-minute dump every Friday beats trying to reconstruct three months of work from memory in April
2.Actively think about glue work before writing your raw notes code reviews, unblocking a teammate, a hallway conversation that changed a decision it’s real work and it’s the first thing people forget to mention
3.Keep every log entry somewhere permanent (a running doc, not a disappearing Slack message) the value compounds the longer you keep it, especially across a manager transition when a new manager has zero context on your work

FAQs

Yes, functionally a developer work log and a brag document are the same underlying habit; this prompt just adapts the format depending on whether you need it for today’s standup or a performance review months from now.

Where this prompt breaks

Known failure modes we hit while testing, so you can spot them before they waste a run.

Tense consistency within standup-format output (present tense required)

Mixes past tense ("Fixed," "Reviewed") with present tense ("Onboarding," "Blocked") within the same bullet list

Raw notes containing a vague, self-flagged-speculative impact claim ("probably saved the company a lot of money")

Passes the vague claim through into the performance-review-format output ("likely saved meaningful revenue") without a number, but also without clearly flagging it as unverified doesn't invent a metric, but doesn't push back on the unsubstantiated claim either

Sources & further reading

Articles, websites, and tools this prompt draws on or recommends.

No Perfect Match?

Generate a custom prompt built around your profession, AI model and goal.

Generate a Prompt →

Claude Prompt for Developer Work Log Description⌄

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.

Send me your AI wisdom

One email a week: new prompts worth using, and what's changed across the models.