day-one-patch

Plan and execute scoped day-one patches with rollback plans and QA gates.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill day-one-patch-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/day-one-patch
Command: npx skills add https://github.com/WindXRan/y3td --skill day-one-patch-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about day-one-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a day-one patch after gold master to fix known bugs before public launch?

To plan a day-one patch after gold master, you scope only approved known issues like S1/S2/P1 bugs under 4 hours, generate a platform-aware rollback plan, implement fixes, and run targeted QA gating before public launch.

What is the best way to scope a day-one patch to avoid launch-day chaos?

The best way to scope a day-one patch is selecting fit-for-day-one items like fix-only minimum viable changes for S1/S2/P1 issues, while deferring risky fixes to patch 1.1 to prevent launch-day chaos.

How do I create a rollback plan for a day-one patch across different platforms?

You create a platform-aware rollback plan for a day-one patch before implementation by defining deployment risk minimization procedures tailored to each platform, ensuring safe rollback if issues arise.

Can I use automated QA gating for release-stage bug triage and patch notes?

Yes, you can use lightweight QA gating for release-stage bug triage by running targeted smoke checks or broader regression, then generate internal and player-facing patch notes based on PASS or PASS WITH WARNINGS results.

When should I defer bug fixes to patch 1.1 instead of including them in a day-one patch?

You should defer bug fixes to patch 1.1 when they are risky, exceed the estimate under 4 hours, or fall outside fix-only minimum viable changes, keeping your day-one patch scope disciplined and safe.

Does day-one patch planning work for pre-launch playtest findings and cert feedback?

Yes, day-one patch planning works for pre-launch playtest findings and cert feedback by reading open bug tracking notes, sprint history, and security audit status to ensure appropriate fixes before or immediately after public launch.