day-one-patch

Plan and coordinate a safe day-one patch for a near-launch game release.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill day-one-patch-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/day-one-patch
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill day-one-patch-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents launch-day chaos by scoping and planning a focused day-one patch after gold master, only for issues that are safe to fix quickly and required for launch readiness.

Core Features & Use Cases

  • Patch scoping from real evidence: Reads the release stage, gate-check verdict, open/pending bugs, recent sprints, and security audit to determine exactly what belongs in a day-one patch.
  • Risk-controlled inclusion rules: Includes only P1/P2 and cert-feedback items that can be fixed in under 4 hours with minimal code-path change; defers riskier work to patch 1.1.
  • Non-negotiable rollback planning: Produces and writes a rollback plan before implementation to ensure the team can revert safely if outcomes are unacceptable.
  • Lightweight targeted QA gate: Re-verifies only the changed areas via smoke checks or broader regression when needed, requiring a PASS or PASS WITH WARNINGS decision.
  • Patch record generation: Writes an internal day-one patch record and drafts player-facing patch notes for community review.

Quick Start

Run the day-one-patch skill with the prompt option selecting the desired scope, for example: "Execute day-one-patch with scope set to known-bugs."

Frequently Asked Questions about day-one-patch

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

FAQPage Schema
What is a day-one patch and when do I need to plan one for a game release?

A day-one patch is a focused, fix-only update applied after gold master is locked but before launch. You need one when known bugs or cert feedback require minimal code changes within a constrained time window to ensure release readiness.

How do I scope eligible fixes for a day-one patch without risking the launch?

Scope a day-one patch by reading open bug records and cert feedback, including only P1/P2 items fixable in under 4 hours with minimal code-path changes. Riskier work should be deferred to patch 1.1 to maintain launch safety.

How do I create a rollback plan before implementing a day-one patch?

Create a rollback plan by documenting the exact steps to revert changes before any implementation begins. This rollback-first workflow ensures the team can safely restore the previous state if QA outcomes are unacceptable.

Can I include complex bug fixes in a day-one patch if we have time before release?

No, day-one patches enforce strict scope discipline by including only P1/P2 and cert-feedback items with minimal code-path changes. Complex fixes should be deferred to patch 1.1 to prevent launch-day instability.

What kind of QA gate is required for a day-one patch deployment?

A targeted QA gate is required, re-verifying only the changed areas via smoke checks or broader regression if needed. Deployment requires a PASS or PASS WITH WARNINGS verdict from this gate before proceeding.

How do I generate patch notes after finalizing a day-one patch?

Generate patch notes by writing an internal day-one patch record and drafting player-facing patch notes for community review. This happens after the patch is scoped, implemented, and passes the targeted QA gate.