Release notes are what you tell your customers changed. You pick the changes worth announcing, and Specsight writes the draft. Open Release notes in the project rail.
For an internal summary of everything that changed, use digests.
Draft release notes
Click New release notes.
- Pick the date range
- Tick the changes to announce
- Add a note in What to emphasise, or leave it empty
- Pick a voice
- Click Generate
You get an email when the draft is ready. Turn it off with Release notes draft ready in account notifications. If it shows Failed, open it to see why and generate a new one.
To announce one release, start from its entry in Changes. Your AI assistant can start a draft too, through MCP. The Standard plan allows 50 drafts a month (plans and limits).
Edit the draft
The draft opens in blocks you can type straight into, and changes save as you go. Switch to Preview to read it as your customers will.
Hover a block for its controls.
- Enter — start a new block
- Backspace — at the start of a block, merge it into the one above
- # or - then a space — turn an empty paragraph into a heading or a list
Enhance rewrites one block in your product’s voice. Leave the box empty for a fresh take, or say what should change.
Publish
Click Publish, leave Notify your team on to email members, and confirm. The notes go live at a public link anyone can read, with no Specsight account.
The button now reads Public. Click it to copy the link. Unpublish takes the page down until you publish again, at the same URL.
Published notes are read-only, so unpublish before you edit or delete them. Copy as gives you Markdown, email-safe HTML or plain text.
Statuses
- Generating — Specsight is writing the draft
- Draft — ready to edit and publish
- Failed — open it to see why, then generate a new one
- Published — live at the public link
Voices
A voice tells Specsight how to write: who the notes are for and how they should read. Open Voices on the release notes list, or Set voice before you have made one.
- Name — how you pick this voice, and the only required field
- Audience — who the notes are for, like non-technical customers
- Tone — how they should read, like warm and plain-spoken
- Structure — how the notes are shaped, like a section per feature
- House rules — anything to follow in every draft
- Language — the language to write in, English by default
Each project can have up to three, and without one Specsight writes in your product’s own voice. Delete a voice and the notes written with it keep their text.