What problem does it solve? Teams shipping internal tools ("toys") through build, test, uat, and production environments often mis-version releases, skip approval gates, or lose track of which stage a tool is in. This Skill gives agents a single runbook for versioning correctly, enforcing founder gates, and recording promotions in the release register. ## Core Features & Use Cases - Version bump rules: Defines patch/minor/major semantics where the change picks the digit, never the promotion, with one-step-only increments and a 1.0.0 rule for first production promotion. - Gate enforcement: Blocks test-to-uat and uat-to-production moves unless a founder's approval is written on the promotion ticket. - Promotion runbook: A seven-step procedure covering release PRs, git tags, register inserts, two-direction verification, and distribution status reporting. - Use Case: An agent is asked to promote a tool from test to uat. It checks the ticket for the founder's call, determines no code changed so no version bump occurs, inserts the register row, verifies visibility for the uat group, and closes out with a Linear comment. ## Quick Start Ask the agent to promote the toy to uat and have it follow the toy-release runbook, checking the founder gate on the ticket first.
