What problem does it solve? After a game's gold master build is locked, known bugs and cert feedback often remain that are too risky to fix in the release build. This Skill turns that chaos into a controlled mini-sprint: it scopes only safe fixes, mandates a rollback plan before any code changes, and gates the patch through a lightweight QA pass. ## Core Features & Use Cases - Patch Scoping: Classifies open bugs by severity, priority, and estimated effort, deferring anything over 4 hours or requiring architecture changes to patch 1.1. - Rollback Planning: Requires a written rollback plan covering platform-specific constraints and trigger conditions before implementation begins. - Lightweight QA Gate: Re-verifies only changed areas via targeted smoke checks or broader regression, producing a PASS/FAIL verdict. - Use Case: Your game passed cert but three P1 bugs surfaced in final playtesting. Use this Skill to scope the fixes, write the rollback plan, implement minimal changes, and produce a signed-off patch record at production/releases/day-one-patch-[version].md. ## Quick Start Use the day-one-patch skill to scope and prepare a day-one patch for my game based on the open bugs in production/qa/bugs.
