What problem does it solve?
It prevents launch-day chaos by planning and executing a day-one patch that only fixes known, safe issues discovered after gold master and before or immediately after public launch, with a defined QA gate and rollback plan.
Core Features & Use Cases
- Patch scoping from release context: Validates the project is in Release-stage and reads stage, gate-check verdicts, open/verified bug notes, sprint history, and security audit status to ensure the patch is appropriate.
- Risk-controlled triage: Selects only fit-for-day-one items (e.g., S1/S2/P1 issues estimated under 4 hours, fix-only and minimum viable change), while deferring risky fixes to patch 1.1.
- Non-negotiable rollback plan: Produces a platform-aware rollback procedure before implementation so deployment risk is minimized.
- Mini-sprint implementation loop + targeted QA: Runs focused implementation for each approved bug, then verifies with a lightweight QA gate (targeted smoke checks or broader regression when necessary), producing a patch record and player-facing notes workflow.
Quick Start
Use the day-one-patch skill to prepare production/releases/day-one-patch-[version].md by scoping the patch to approved known bugs, generating a rollback plan first, implementing only the approved fixes, and running a targeted QA gate.