What problem does it solve? Shipping a Todero release involves many coordinated steps—changelog drafting, canary validation, smoke testing, stable promotion, GitHub Release creation, and announcement follow-up—and missing any one of them can ship a broken or undocumented release. 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 case tree (parent release case plus blog_post and tweet_storm children) via the Todero 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, promote it to stable on npm, create the GitHub Release, and file the announcement follow-up tasks. ## Quick Start Ask the agent to ship the stable Todero release from the latest verified canary on master.