What problem does it solve?
It helps teams avoid launch-day chaos by planning and gating a limited, fix-only patch for issues found after gold master but before or immediately after public launch.
Core Features & Use Cases
- Patch scoping with guardrails: Limits inclusions to safe, fast fixes (no new features, no refactoring, minimal viable changes) using severity/priority and effort thresholds.
- Rollback plan requirement: Forces a rollback procedure to be defined before implementation so deployment risk is controlled.
- Targeted QA gate: Runs a lightweight re-verification focused on changed areas, escalating to broader regression when needed.
- Release record generation: Produces an internal patch record and supports player-facing patch notes preparation.
Quick Start
Run the day-one-patch skill and answer the prompts to approve the proposed scope, write the rollback plan, implement the approved fixes, pass the QA gate, and generate the day-one patch release record.