write-a-release-announcement

# write-a-release-announcement Announce what is actually available to the stated audience. ## When to use - Use after release readiness and availability are independently confirmed. - Do not call planned, partially rolled out, or unverified work live. ## Procedure 1. Confirm release name, exact version, availability, regions, cohorts, access, date, and owner. 2. Identify audience, problem, user-visible value, and the most important changed behavior. 3. State what is new, what is unchanged, prerequisites, limitations, known issues, and compatibility. 4. Explain any required action, migration, deadline, support, rollback, or opt-out. 5. Link documentation, evidence, status, accessibility, security, privacy, and feedback routes as relevant. 6. Remove invented superlatives, unsupported metrics, internal jargon, and ambiguous timing. 7. Verify links and release state from the user-facing surface immediately before publication. ## Done - A release announcement draft records version, availability, audience value, changes, limitations, actions, support, and links - Live-state, cohort, claim, version, limitation, link, accessibility, and owner-approval checks verify the announcement