Version 0.3.0 of devlog is out. It's a plugin for Claude Code that keeps a project's progress log, decisions and tickets in plain markdown, and lets Claude maintain them while it works. This version adds two skills: releases and posts.
The original version was a post in Hebrew on X, published October 12, 2026.
The releases skill
Every file that carries the version number is listed once in docs/RELEASES.md. A gap between the files and the tags is flagged at the end of every session. Entries in the progress log get an [unreleased] stamp and are switched to the version number at the moment of the cut, so the changelog is written from the entries themselves.
The posts skill
A backlog of post ideas generated from the progress log, the decisions and the tickets, never from client emails. One file per post per platform, with the text as it was published. Includes a privacy check that runs to see that nothing that shouldn't be there leaked. You can feed replies to the post back in and turn them into tickets, an FAQ or decisions.
Still skills in markdown only: no hooks, no scripts, no dependencies.
This post is the first one filed through the posts skill inside the plugin's own repo.
Why keep all of this in the project?
For me it's aware of everything: spec documents, presentations, vendors, calls, emails, posts and so on. I basically manage the whole project inside Claude Code. And you can ask it, for example: why did we do something this way? And it can pull out for you that in an email from date x we closed it with the client, and the reasons. Or give you the brakes on a feature that already came up.
In the end, if we don't do this, we won't know at all what's going on in the project, because the code isn't ours anymore :)
Get devlog
The code is on GitHub: github.com/razamit/claude-devlog
The earlier versions are in How to Give Claude Code a Project Memory (progress log, decisions, tickets) and devlog 0.2.0 (client emails and calls).
FAQ
What does the devlog releases skill do?
Every file that carries the version number is listed once in docs/RELEASES.md. A gap between the files and the tags is flagged at the end of every session, and progress log entries get an [unreleased] stamp that is switched to the version number at the cut, so the changelog is written from the entries themselves.
Does devlog need hooks or scripts?
No. It's still skills in markdown only: no hooks, no scripts, no dependencies.