write-release-noteslisted

# write-release-notes ## Overview `tb-streamer` is a Hono HTTP/WebSocket streaming server for Claude Code sessions. It ships in two layers of changelogs: - **`CHANGELOG.md`** at the repo root — auto-generated by semantic-release, one line per conventional commit. Granular, machine-friendly, regenerated on every release tag. **Do not hand-edit.** - **`docs/release-notes/YYYY-MM-DD-<milestone>.md`** — the human narrative of what shipped in a milestone, why it matters, what's deferred, breaking changes, operator-facing additions. Written once per milestone, by hand (or by this skill), and lives in git as the durable story. This skill drafts the second layer. It produces a single markdown file under `docs/release-notes/` based on the structure of `docs/release-notes/_template.md`, scoped to the commits and PRs that landed since the last release-notes file. The two layers coexist deliberately. `CHANGELOG.md` answers "what commits shipped in v1.5.2?". This directory answers "what was Milestone B actually about, and what should an operator or mobile-client author know before consuming it?". ## When to use Invoke this skill when: - A named milestone (Milestone B, Milestone C, Plan 4, etc.) is ready to merge to `main`. - The final commit for that milestone is on the feature branch. - The merge-to-main PR is open (or about to be opened) but not yet merged. **Trigger phrases that should call this skill:** "write release notes for Milestone X", "draft release notes", "/write-rel