One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill day-one-patch-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/day-one-patch
Command: npx skills add https://github.com/MichaelSolati/mkai --skill day-one-patch-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unplanned, overly broad day-one patches for game launches often introduce more stability risks than they fix, especially when teams rush to address post-gold-master bugs without proper scoping or safety guardrails. This Skill eliminates that risk by providing a structured, low-overhead workflow to deliver only safe, necessary fixes before or immediately after launch.

Core Features & Use Cases

  • Strict Scope Filtering: Automatically classifies open bugs to include only safe, low-effort fixes (under 4 hours of work, no new features or refactoring) and defers riskier changes to post-launch patches.
  • Mandatory Safety Guardrails: Requires a formal rollback plan and lightweight QA sign-off before any patch code is written, preventing unvetted changes from going live.
  • Use Case: A game studio that just locked their gold master build but received cert platform feedback requiring 2 minor fixes, plus 3 critical playtest bugs, can use this Skill to deliver a minimal, validated patch without derailing launch day operations.

Quick Start

Use the day-one-patch skill to prepare a fully scoped, QA-gated day-one patch for your upcoming game launch, including a rollback plan and approval checklists for your team.

Frequently Asked Questions about day-one-patch

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

FAQPage Schema
How do I scope a safe day-one patch for a game launch?

To scope a safe day-one patch, classify open bugs to include only low-effort fixes under four hours and defer riskier changes to post-launch updates. This strict filtering prevents unplanned high-risk post-release fixes from destabilizing your live game.

What is a day-one patch and when do I need it for game development?

A day-one patch is a minimal update applied immediately after a game's gold master lock to address cert platform feedback or critical playtest bugs. You need it to resolve known safe-to-fix issues before or right after public launch without derailing operations.

How do I implement launch preparation patches without introducing new stability risks?

Implement launch preparation patches safely by enforcing mandatory rollback planning and a lightweight QA gate before writing any patch code. These safety guardrails prevent unvetted changes from introducing new stability or security risks to the live game.

Can I include new features or refactoring in a day-one game patch?

You cannot include new features or refactoring in a day-one game patch. The workflow limits changes to safe, low-effort fixes under four hours to eliminate stability risks, automatically deferring any broader changes to post-launch patches.

What's the best way to handle cert platform feedback after locking a gold master build?

The best way to handle cert platform feedback after locking a gold master build is applying a structured, low-overhead workflow to deliver only necessary, validated fixes. This approach ensures you meet certification requirements without risking launch day stability.