Turn approved software changes into accurate release notes with source traceability, audience variants, migration actions, known issues, and a publication handoff.
Release notes often begin with the least reliable source: a pile of commit messages. That is how planned work appears as shipped, staged features look universally available, internal refactors become vague benefits, and a missing migration path gets hidden behind a polished bullet.
Release Notes starts with the release boundary: product, version, cutoff, audience, channels, authoritative records, and separate read, draft, approve, publish, notify, and delivery-verification authority. It builds an evidence ledger and keeps confirmed, reported, inferred, missing, conflicting, and post-cutoff facts distinct.
The workflow creates one canonical change record before writing audience variants. It classifies additions, behavior changes, fixes, deprecations, removals, security summaries, known issues, and internal work. Public notes include only evidence-backed changes in the stated rollout scope. Developer and administrator variants can add relevant detail without changing availability, compatibility, deadlines, actions, or known-issue state.
Breaking changes get explicit migration and verification steps. Deprecations need a replacement and an approved removal date or decision owner. Known issues preserve affected scope and verified workarounds. Security notes require authorized public wording. Planned work, unaccepted fixes, unsupported performance claims, and rolled-back availability stay out of final notes.
The package includes a canonical JSON release-note contract and a local read-only checker. The checker validates source references, claim states, public-item eligibility, breaking-change migration fields, deprecation and known-issue records, approved security summaries, critical unknowns, and publication authority. It cannot inspect a live deployment, decide whether a source is authoritative, approve wording, publish a channel, or prove delivery.
Version 1.0.0 was evaluated on 25 July 2026 through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. Across three cases, the candidate scored 100, compared with 82.08 for the same agent without the skill and 88.75 for the exact free upstream. It passed every case and led the comparison arms by 17.92 and 11.25 points overall. The cases covered mixed shipped and staged SaaS changes, a blocked breaking API release, and a rollback correction with an approved security note. This evaluation measures the supplied cases; it does not prove that a real release shipped or that a note is safe to publish.
The package SHA-256 is db768adcd7a7301c72135ba9a4f632e6d417e59a18dcc221aa05998192d5e5ad. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The release manifest confirms resumable export for everyone and SSO mapping for 25% of Enterprise workspaces. A mobile feature is merged but disabled. A billing fix has no acceptance record. Marketing asks to call every item available.
Output
Source-bound notes that include the shipped export, name the exact staged SSO scope, exclude planned and unaccepted work, reject unsupported claims, and end at ready for review because publication is not authorized.
Input
Version 4.0 renames a response field, removes an endpoint, changes pagination, and fixes a signature flaw. The candidate has not shipped. Migration verification, rollback, endpoint guidance, and public security wording are missing.
Provide the product and version, release cutoff and timezone, intended audiences and channels, authoritative release or acceptance record, merged work and test evidence, rollout scope, migration or deprecation guidance, known issues, approved security wording, style rules, and separate authority to draft, approve, publish, notify, and verify delivery. Ask for public notes, developer or administrator variants, a correction, or the canonical JSON record.
Product, component, version or release ID, cutoff and timezone, comparison version, intended audiences, channels, and rollout scope.
Release manifest or acceptance record plus relevant pull requests, tickets, tests, deployments, migration guides, documentation, security approvals, support notes, source owners, and observation times.
Product terminology, style guide, localization needs, compatibility policy, and legal, privacy, security, billing, or compliance review requirements.
Separate permission to read, draft, approve, publish, notify, and verify channel delivery.
SKILL.md; release-note record contract; read-only canonical record checker; Codex interface metadata
No reviews yet.
Output
A blocked draft with precise breaking-change facts, known affected versions and security action, missing migration and disclosure gates, owner-bound decisions, and no claim that the release is available.
Input
The original changelog says offline pinning shipped. An authoritative rollback disabled it after data-index corruption. A post-cutoff chat claims it is fixed without acceptance evidence. A separate security summary is approved.
Output
A correction draft that removes the availability claim, records the known issue without inventing a workaround, includes the approved security upgrade action, preserves cutoffs, and does not claim the correction was published.
Creator
Ttalvio
