What problem does it solve? Critical bugs in shipped games need immediate fixes, but rushing patches without process causes regressions and untracked changes. This Skill provides a structured emergency fix workflow that bypasses normal sprint processes while maintaining a full audit trail, approvals, and rollback plans. ## Core Features & Use Cases - Severity Assessment: Classifies bugs as S1 (critical), S2 (major), or S3 (redirect to normal workflow) with user confirmation before proceeding. - Hotfix Record and Branching: Creates a documented hotfix record in production/hotfixes/ and optionally creates a git hotfix branch with user approval. - Approval and QA Gates: Collects sign-off from lead-programmer, qa-tester, and producer subagents, then routes through a QA re-entry gate (smoke check, targeted team-qa, or full QA) before deployment. - Use Case: A live game has a save-data corruption bug. Invoke the hotfix workflow to assess it as S1, create the hotfix branch, implement the minimal fix, gather three approvals, pass the QA gate, and deploy with a documented rollback plan. ## Quick Start Use $ai-game-studio:hotfix to run the emergency fix workflow for the reported save corruption bug and produce a deployment-ready hotfix record.
