Quartz 5

Keep a Worklog: One Markdown File Per Day, Wired Into Claude Code

Properties1
tagsnote, productivity, claude-code

2 min read

Summary

The author advocates keeping a worklog — a daily record of what you work on — as one Markdown file per day in a repository connected to Claude Code, a habit he’s maintained for a couple of years. Throughout the day he throws raw items at Claude, which converts them into tidy, human-readable bullet points; at day’s end he posts the summary to a team progress Slack channel. He also has a /checkpoint command that summarizes progress since last week into a Markdown file.

作者主張寫工作日誌——逐日記錄你做了什麼——以每天一個 Markdown 檔的形式存於連接 Claude Code 的儲存庫，他已維持此習慣數年。白天他把零散事項丟給 Claude，由它轉成整齊、人類可讀的條列；一天結束後再把摘要貼到團隊的 progress Slack 頻道。他另有一個 /checkpoint 指令，將上週以來的進度彙整成一個 Markdown 檔。

Key Points

  • Worklog format: one Markdown file per day, kept in a repo wired to Claude Code.
  • During the day, raw notes get tidied by Claude into readable bullet points.
  • End-of-day summary shared to a team progress Slack channel for visibility.
  • A /checkpoint slash command summarizes progress since last week into a Markdown file.
  • Benefits: accountability, day/week tracking, and checking alignment against a bigger plan.

Insights

This is a minimal, low-friction instance of the same pattern running through the vault’s other clippings: durable Markdown as the source of truth, with the LLM acting as a formatting/summarization layer rather than the store. The worklog doubles as an external memory artifact — exactly the “prosthetic memory” BensonTWN describes — and the /checkpoint command is the same slash-command-as-automation idiom Boris Cherny and Teresa Torres use. Sharing to Slack turns a personal habit into team coordination at near-zero marginal cost.

Connections

Raw Excerpt

During the day, I throw stuff at Claude and it translates into nice and tidy bullet points that are human-readable.

Graph View