drafting-changelog-entrieslisted

# Drafting Changelog Entries Turn a finished build session into an accurate `CHANGELOG.md` entry — accurate meaning every "Added" line is checked against the actual repo state, not against what was intended or what a build prompt asked for. Intent and outcome drift, especially across a long session; this skill exists specifically to catch that drift before it ships as a false claim in a changelog. ## Why this matters here specifically SkillArtisan's own build process (the master spec + the Stage 1-4/5-6 build prompts) explicitly warns against exactly this failure mode: "don't mark anything done that isn't verifiably true of the repo." A changelog entry is a public claim about what a version does. Writing "Added: X" when X was planned but not actually finished — or was finished differently than planned — is the same category of error the master spec's own release checkpoint guards against, just at the documentation layer instead of the code layer. ## Process 1. **Gather what actually happened.** Prefer `git log`/`git diff` against the previous release tag if this is a git repo; otherwise, work from the session's own record of what was built (files created/edited, scripts run, tests passed). Don't work from the build prompt's task list alone — a task list describes intent, not outcome. 2. **Cross-reference against the Gap Table**, not just against the task list. Read the relevant Gap Table rows (`skill-artisan-master-spec.md`'s "Gap Table" section, or whatever this projec