Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/day-one-patch
Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.
Passed 18 of 19 test cases with the skill, and 7 of 19 without it.
and 10 more in the full report
11 fixed7 passed either way1 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When presented with the proposed day-one patch scope options, the lead producer selects `[C] No day-one patch needed` because all open issues are low risk. What is the required next step?
| Checked | Without skill | With skill |
|---|---|---|
| Directs user to run /launch-checklist when scope option C is selected. | Missed | Passed |
The instructions your model reads when the skill loads.
Every shipped game has a day-one patch. Planning it before launch day prevents chaos. This skill scopes the patch to only what is safe and necessary, gates it through a lightweight QA pass, and ensures a rollback plan exists before anything ships. It is a mini-sprint — not a hotfix, not a full sprint.
When to run:
Day-one patch scope rules:
Output: production/releases/day-one-patch-[version].md
Read:
project.stage in project.yaml (fallback production/stage.txt) — confirm project is in Release stageproduction/gate-checks/ — read the release gate verdictproduction/qa/bugs/*.md — load all bugs with Status: Open or Fixed — Pending Verificationproduction/sprints/ most recent — understand what shippedproduction/security/security-audit-*.md most recent — check for any open security itemsIf the resolved stage (project.yaml → stage.txt) is not Release or Polish:
"Day-one patch prep is for Release-stage projects. Current stage: [stage]. This skill is not appropriate until you are approaching launch."
Check the premise, do not assume it. This whole skill rests on there being a gold master that already passed a release gate — that premise is what justifies its lightweight QA pass instead of a full one. So verify it rather than inferring it from the stage value:
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.