What problem does it solve? Teams often ship software based on partial evidence—passing unit tests or a healthy local server—while missing stale generated clients, broken browser-facing workflows, or unresolved security findings. This Skill enforces a fail-closed release decision process that requires current, revision-bound evidence across app health, release gates, security, and operational readiness before recommending publish. ## Core Features & Use Cases - Bounded GO/NO-GO decision: Produces exactly one release decision with a required report covering App health, Release evidence, Security readiness, Operational readiness, and Accepted exceptions. - Evidence gate enforcement: Treats missing, stale, blocked, or unreached gates as unresolved, rejects stale generated API clients, and blocks on unresolved high/critical security findings. - Failure closure and repair fan-out: Records every gate as PASS, FAIL, BLOCKED, NOT REACHED, or MISSING, keeps same-objective repairs in one durable task, and avoids unbounded follow-up task chains. - Use Case: A release manager asks "Can we go live today?" after unit tests pass but browser smoke tests and the security review were never run. The Skill returns NO-GO, names the exact missing evidence, and stops without recommending publish. ## Quick Start Ask the assistant to check whether the app is production-ready and give a GO or NO-GO release status for the current commit.