day-one-patch

Plan and execute day-one patches with rollback and QA guardrails.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill day-one-patch-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: day-one-patch
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/day-one-patch
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill day-one-patch-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Day-one patch planning and governance to safely patch releases after gold master, with rollback and QA guardrails.

Core Features & Use Cases

  • Domain routing and release-context awareness for patches
  • Scope classification, risk gating, and a one-day patch window
  • Rollback planning and production-patch record generation

Quick Start

Initiate the end-to-end day-one patch workflow to scope, implement, QA, and record a production patch.

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 and execute a safe day-one patch after a game launch?

A day-one patch is planned and executed through a deterministic workflow that governs patch scope, rollback procedures, QA guardrails, and documentation across platforms after a gold master release.

What is the best way to manage release risk during a one-day patch window?

Release risk during a one-day patch window is managed through scope classification and risk gating, ensuring that only approved changes pass through phase gates before production deployment.

How does rollback planning work for day-one product release patches?

Rollback planning for day-one patches establishes predefined recovery procedures and guardrails, allowing production environments to safely revert changes if post-launch issues occur during the patch window.

Can I use this workflow for day-one patches across multiple platforms?

Yes, the day-one patch workflow applies to game releases and product launches, governing patch scope, rollback, QA, and documentation across platforms with release-context awareness.

What artifacts do I need to generate when scoping a post-launch patch?

Sccoping a post-launch patch requires generating production-patch records and documentation artifacts, which are enforced as outputs upon passing phase gates in the deterministic workflow.

When should I not apply a day-one patch to a gold master release?

A day-one patch should be avoided when required inputs for scope classification, risk gating, or rollback planning are unavailable, as the deterministic workflow enforces strict phase gates before deployment.