What problem does it solve? Cutting a software release involves many error-prone steps: assembling accurate change lists, writing honest release notes, coordinating documentation, bumping versions, tagging, and announcing. This Skill provides a gated, step-by-step run-book that prevents common release mistakes like documenting unshipped features, tagging untested commits, or sending bulk email without a working unsubscribe. ## Core Features & Use Cases - Gated 11-step workflow: Each step (pre-flight, versioning, change assembly, accuracy verification, notes writing, docs coordination, sign-off, tagging, announcement, verification) has an explicit gate that must be cleared before proceeding. - Accuracy gate for release notes: Verifies every headline feature against actual running code rather than design documents, distinguishing shipped defaults from opt-in previews. - Deployment ordering enforcement: Detects Gateway hub method changes via git diff and requires the hosted Gateway to be deployed before the release tag is pushed. - Use Case: A maintainer types "/release-manager" and the agent fetches origin, proposes v1.2.0, assembles and verifies the change list, writes docs/public/release-notes/v1.2.0.md, coordinates the internal changelog session, and prepares the version-bump pull request so the human only has to publish the tag. ## Quick Start Ask the agent to cut a release by saying "prepare a release" or invoking /release-manager, and it will walk you through each gated step starting with pre-flight checks.
