dispatches.dev

# dispatches `dispatches` is a shareable agent skill for repositories that want a running, branch-scoped daily record of intent. The core idea is simple: replace stray plan files and vague session memory with a chronological set of dispatch entries in `.agents/dispatches/<date>-<branch>.md`. Each entry acts like a terse captain's log. It explains what the session was trying to do, what changed since the last entry, and how to interpret the work, without duplicating the code diff. ## Why this exists This project started as a "journal" or ".diary" workflow. The original need was not better changelogs. It was better context: - every work session should start by recording what has changed since the last meaningful session - repo-level movement still matters, even when nobody has actively developed on the current branch - plans are only useful as points-in-time, so they should be embedded into the dispatch for that day instead of lingering as standalone files - if a chat thread spans multiple days, it should still produce multiple dated entries That workflow later settled on `.agents/dispatches` as the canonical home for those records, and this package captures that convention as a reusable skill. ## What the skill enforces - one dispatch file per date and branch - an `## Editor's Note` at the top that summarizes intent and changes in context - updates to the dispatch as commits happen during the session - migration of standalone plan documents into the relevant dated dispatch entry, followed by removal of the original files - chronological history that explains why work happened, not just what changed ## Packaging The repository is structured as a root-level skill so current `skills` tooling can discover it directly: ```bash npx skills add <owner>/dispatches ``` It is also publishable to npm as `dispatches`. The package includes a small helper CLI: ```bash dispatches verify dispatches path dispatches export ./some-directory ``` On this machine, npm cache permissions required using a temporary cache during verification and publish: ```bash npm_config_cache=/tmp/npm-cache npm publish --access public ```