Skills I've built

narrative-docs-update: the record, in-repo

After any coherent arc of work, the story goes into the work's own repository, in its docs folder, where later processes actually find it.

What it does

After any coherent arc of work, the story of what happened goes into the work's own repository, in its docs folder, with a changelog entry alongside. The habit exists because records written anywhere else turned out to be invisible to the systems that needed them.

Trigger

The end of a coherent arc of work: a feature landed, an incident closed, a decision taken.

What you need

• A per-project home for the record, inside the project itself.
• The rule that the record is written as part of the work, not as an optional extra.

Setup sketch

Adopt the placement rule first: narrative records live in the work's own repo, in a predictable folder, so downstream readers, human and agent, ingest them by convention rather than by search.

Deep dive: Grow your own skills →