What problem does it solve? Shipping a stable Paperclip release involves many coordinated steps—changelog drafting, canary validation, smoke testing, npm promotion, GitHub Release creation, and announcement follow-up—and missing any one of them leaves the release incomplete or broken. This Skill orchestrates the entire maintainer release workflow so nothing is skipped. ## Core Features & Use Cases - End-to-End Release Orchestration: Walks through candidate selection, changelog drafting via the release-changelog skill, verification gates, canary validation, Docker smoke testing, and stable promotion. - Commit-Driven Versioning: Enforces the YYYY.MDD.P versioning model where canaries publish automatically from master and stable releases are manually promoted from a tested source ref. - Release-Content Case Tracking: Creates a deterministic parent release case with blog_post and tweet_storm child cases via the Paperclip Cases API for announcement follow-up. - Use Case: When leadership says "ship the release," use this Skill to verify the latest canary, smoke test it with docker-onboard-smoke.sh, promote it to stable via the release workflow, and create the GitHub Release and announcement cases. ## Quick Start Ask the agent to ship the stable Paperclip release from the latest verified canary on master.