# 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.

From the [Skills I've built](../index.md#skills) section of [The Muse Field Guide](../index.md).

## 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.

## Where this came from

The skill exists twice in this library: the current one, and its predecessor kept in place as a redirect after being formally superseded on October 18, 2026. Nothing broke when the workflow was replaced, because the old name still resolves.

Deep dive: [Grow your own skills](../deep-dives/skills.md)

Related resources: [ship: the one-word closing ritual](ship.md), [Corrections land in files same-day](corrections-land-same-day.md)

Canonical page: https://www.niclydon.io/muse/items/narrative-docs-update.html