Content
Release Notes Truth Sweep
Turn internal change lists into release notes that match the product users can touch.
Use when
Release notes are being drafted from PR titles, tickets, or internal updates and may overstate what users actually get.
Intermediatedifficulty
Contentcategory
Mia daily expansionsource
Cadence
Before publishing release notes or changelog updates
Verification
Every public note maps to shipped user-visible behavior, and unverifiable or sensitive claims are cut, narrowed, or queued for approval.
Structured loop spec
| Field | Value |
|---|---|
| Name | Release Notes Truth Sweep |
| Category | Content |
| Trigger | Before publishing release notes or changelog updates |
| Objective | Turn internal change lists into release notes that match the product users can touch. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Collect candidate changes from merged PRs, tickets, commits, demos, and product notes for the release window.; Rewrite each candidate as a user-visible change, known fix, migration note, or internal-only item.; Check the product, screenshots, docs, or acceptance tests for proof that each public-facing claim shipped.; Remove implementation trivia, roadmap promises, private customer details, security-sensitive wording, and anything that needs approval.; Stop when every published line has evidence, owner approval where needed, and a clear user implication. |
| Verification | Every public note maps to shipped user-visible behavior, and unverifiable or sensitive claims are cut, narrowed, or queued for approval. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- Collect candidate changes from merged PRs, tickets, commits, demos, and product notes for the release window.
- Rewrite each candidate as a user-visible change, known fix, migration note, or internal-only item.
- Check the product, screenshots, docs, or acceptance tests for proof that each public-facing claim shipped.
- Remove implementation trivia, roadmap promises, private customer details, security-sensitive wording, and anything that needs approval.
- Stop when every published line has evidence, owner approval where needed, and a clear user implication.
Prompt
Run the Release Notes Truth Sweep loop. Given a release window, collect merged PRs, tickets, commits, demos, and product notes. Convert candidates into user-visible changes, fixes, migration notes, or internal-only items. Verify each public claim against shipped behavior, screenshots, docs, or tests. Cut implementation trivia, private details, security-sensitive wording, and future promises unless approved. Return the final notes, evidence map, and approval queue.