What problem does it solve? After a game's gold master is locked, known bugs and cert feedback still need fixing before or right after launch, and fixing them ad hoc risks destabilizing the release. This Skill turns that chaos into a controlled mini-sprint with strict scope rules, a mandatory rollback plan, and a lightweight QA gate. ## Core Features & Use Cases - Scope Classification: Evaluates every open bug against severity, effort, and risk criteria to decide what belongs in the day-one patch versus patch 1.1. - Rollback-First Planning: Requires a written rollback plan covering platform constraints and trigger conditions before any code changes begin. - Targeted QA Gate: Runs a scoped smoke check or regression pass on only the changed areas, then produces a patch record with approvals and player-facing notes. - Use Case: Your release candidate passed the gate but three P1 bugs and one cert feedback item remain. Run this Skill to approve a safe fix scope, implement minimal fixes via subagents, verify them, and ship a documented day-one patch with rollback coverage. ## Quick Start Ask the AI to prepare a day-one patch for the current release by scoping open bugs, defining a rollback plan, and gating the fixes through QA.
