AI agent skill · by @nightly-labs

Launch Notes

Turn completed changes into clear release notes and launch messages, with verified scope and user impact.

Archived 2026-10-23 · Source updated 2026-10-11. Check the original repository for the latest version.

SKILL.md instructions

# Launch Notes

## Inputs

Use merged changes, issue summaries, or an approved release scope. Establish the audience and release identifier when available.

## Workflow

1. Group changes by what users can now do or what problem is fixed. Remove implementation detail that does not help the reader act.
2. Keep shipped work separate from planned work. Do not infer availability from an open task or an unmerged change.
3. Call out a breaking change with the affected user, required action, and known deadline. Do not invent migration instructions.
4. Write a concise release note first. Produce an announcement or internal handoff only when requested, with the same factual scope.

## Deliverable

Return a release heading, grouped improvements and fixes, required user actions, and unresolved facts to confirm before publication. Leave publication to the requested workflow.