What problem does it solve? Critical bugs in a shipped game cannot wait for the normal sprint cycle, but rushing a fix without process risks breaking something else. This Skill provides a controlled emergency fix workflow with a full audit trail, so S1 and S2 issues get resolved fast without skipping review, testing, or rollback planning. ## Core Features & Use Cases - Severity Triage: Classifies bugs as S1 (critical), S2 (major), or S3 (redirect to normal bug workflow) with user confirmation before proceeding. - Audited Hotfix Lifecycle: Creates a hotfix record file, a dedicated git branch, and collects parallel sign-offs from lead-programmer, qa-tester, and producer subagents. - QA Re-Entry Gate: Determines whether a smoke check, targeted team-qa pass, or full QA sprint is required before deployment. - Use Case: A live game has a save-data corruption bug. Invoke the hotfix workflow to assess it as S1, create a 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.