Diary

An implementation diary captures the narrative of your work: what you did, why, what worked, what broke, what was tricky, and what needs review. The concept of "diary" activates existing behavioral patterns without requiring much engineering -- the model already knows what a diary is.

Working Loop

Follow this cycle for each meaningful unit of progress:

Implement -- make the code change
Update diary -- add or update the current step in the diary file
Commit together (when asked) -- when the user asks for a commit, include the diary file alongside the code it documents. Invoking this skill is not itself a commit request -- wait for the user to ask before running git commit.

A "step" is a logical chunk of work, not necessarily a single commit. Examples: "wire up the API endpoint", "debug the flaky test", "research how the auth middleware works".

File Location

Diary files live at docs/diary/YYYY-MM-DD-<slug>.md relative to the project root.