---
title: "Give a long task a worklog"
description: "Keep decisions and open questions that would otherwise disappear with the chat."
---

> Documentation Index
> Fetch the complete documentation index at: https://afg.callum.website/llms.txt
> Use this file to discover all available pages before exploring further.

# Give a long task a worklog

Use a short `LOG.md` in the project when work may outlast the chat. Keep the goal, decisions made in conversation, open questions, and the next action. Update it when one of those changes.

I tried Eric Provencher’s worklog idea on a design-system project. The log started repeating project status I could already find elsewhere. The useful part was keeping the feedback I’d given in chat and the work it left open.

I still use a worklog on long tasks. It helps me keep track of decisions and loose ends as the conversation moves on.

[Eric Provencher’s original post](https://x.com/pvncher/status/2093098130312974798).

Source: https://afg.callum.website/give-a-long-task-a-worklog/index.mdx
