cut-release
Cut Release
Prepare and cut a release as a strict sequence of gates. Create one todo per step below and work them in order.
The stop rule: any step that fails means STOP — report exactly what failed and what remains, and leave the repo un-released. There are no partial releases: no tag without a passing build, no notes for artifacts that do not exist, no "we'll fix it after tagging."
Terminal reject vs stop rule: after a stop-rule failure, ask once whether the
user issues an explicit terminal reject. Yes → REQUIRED SUB-SKILL: use
record-verdict with verdict release-reject, Boundary-Type: release, durable
evidence inline; leave the repo un-released. No / silence / "fix later" → no
decision record (mechanical stop alone is not a terminal verdict). The same
release-reject write-handoff applies if the user rejects at version or tag approval.
Stop-rule discipline is unchanged: no partial releases.
Read the repo's commands from docs/agents/project.md (verify commands, release steps, smoke command). If it is missing, say so, suggest configure-repo, and ask the user for the commands before proceeding.