What problem does it solve? Shipping software without a defined release process leads to ambiguous version bumps, unmerged hotfixes, unrehearsed rollbacks, and feature flags that outlive their features. This Skill provides a structured release management workflow covering the full lifecycle from scoping to close. ## Core Features & Use Cases - Nine release modes: Plan, Cut, Qualify, Roll, Flag, Hotfix, Rollback, Notes, and Audit, each with a defined output such as a release plan, exit checklist verdict, or rollback procedure. - Versioning and branching discipline: Enforces semver/calver scheme selection, MAJOR/MINOR/PATCH bump rules, release branch merge-back requirements, and hotfixes branched from tags rather than mainline. - npm package adaptation: Tailors the process for registry-published libraries like react-basics-ui, replacing staged rollouts with dist-tags, rollback with deprecate-and-roll-forward, and deriving the bump from a .d.ts API diff. - Use Case: A maintainer preparing the react-basics-ui 2.0.0 release uses the Skill to confirm the breaking API changes require a MAJOR bump, run the pre-publish checklist (lint, tsc, vitest, build, npm pack --dry-run), and draft migration notes for each removed prop. ## Quick Start Ask the assistant to plan the next release of the package, including the version bump justification, pre-publish checklist, and release notes with migration steps.