What problem does it solve? Coordinating the final cut-over of a release — merging the PR, watching the deploy, smoke-checking production, monitoring the window, and tagging — is error-prone when state lives in conversation memory or repo-local files, especially across sessions, machines, and agents. This Skill drives the entire ship flow against the shared Marshall store so every step is recorded, resumable, and never re-executed. ## Core Features & Use Cases - Deploy mode: Merge the release PR, watch a Laravel Cloud (or manual) deploy, run an HTTP smoke check, monitor a timed window, and tag the merge commit — each step recorded via set_deploy_step. - Tag mode: For releases that ship as tagged packages (Packagist), drive merging → dating → tagging → releasing → done via set_ship_step, with the operator running irreversible git/GitHub commands. - Resumability and safety gates: release_get is read on every invocation so a resumed run never re-merges or re-deploys; the store's readiness gate blocks shipping when unresolved high-severity findings exist. - Use Case: After /marshall:release-wrap clears a release, invoke this Skill to merge PR #42, watch the Laravel Cloud deploy, smoke-check the production URL, monitor for 30 minutes, and tag v0.21.0 on the merge commit — all recorded on the store's Deploy record. ## Quick Start Say "deploy the release" or run /release-deploy to start the gated cut-over flow for the current release.