hotfix

Explicit invocation only: Only run when user requests /hotfix.

Phase 1: Assess Severity

Severity	Criteria	Action
S1 Critical	Unplayable, data loss, security vuln	Hotfix immediately
S2 Major	Significant feature broken, workaround exists	Hotfix within 24h
S3+	Lower severity	Recommend normal bug fix workflow, stop

Phase 2: Create Hotfix Record

Draft record with: short description, date, severity, reporter, status IN PROGRESS, sections for Problem (player impact), Root Cause (fill during investigation), Fix (fill during implementation), Testing, Approvals (qa-engineer, qa-director, delivery-manager checkboxes), Rollback Plan.

Ask to write to production/hotfixes/hotfix-[date]-[short-name].md.

Phase 3: Create Hotfix Branch

If git initialized: git checkout -b hotfix/[short-name] [release-tag-or-main]

Phase 4: Investigate and Implement

Minimal change only — NO refactoring, cleanup, or features alongside. Run targeted tests, check regressions in adjacent systems. Update record with root cause, fix, test results.

Phase 5: Collect Approvals (Parallel)

Spawn via Task, only the ones installed in .claude/agents/ (check first: an uninstalled name falls back to a general-purpose agent that reads broadly and returns nothing useful):

Agent	Question to ask it
qa-engineer	correctness and side effects of the fix
qa-director	regression scope: what else must be re-tested
delivery-manager	deploy timing and comms

Every agent that ran must APPROVE before proceeding. If none is installed, do the three checks inline and record that in the hotfix record instead of claiming approvals that never happened.

Phase 5b: QA Re-Entry Gate

Spawn qa-director (or qa-engineer if that is what is installed) with hotfix description, affected system, regression results, caller list (grep). If neither is installed, pick the verdict yourself from the regression results and say so in the hotfix record.

Skills below that ship with other profiles may not be installed: check .claude/skills/<name>/ first, and if it is missing offer /arcane-add <name> instead of running it.

QA Verdict	Action
Smoke check sufficient	/smoke-check → if PASS, proceed
Targeted QA pass	Manual pass on the affected system with the plan from /qa-plan [affected-system] → if PASS, proceed
Full QA required	Full manual pass with the plan from /qa-plan sprint — delays deploy but prevents bad patch

Do not skip this gate.

Phase 6: Update Bug Status and Deploy

Update original bug file: fixed in (branch/commit), date, status "Fixed — Pending Verification". Output deployment summary: severity, root cause, fix, QA gate result, approvals, rollback plan. Merge to BOTH release branch AND development branch.

Rules

• MINIMUM change — no cleanup or refactoring
• Rollback plan documented before deployment
• Merge to both release AND dev branches
• Post-incident review within 48h
• If fix needs >4h → escalate to the technical lead (technical-director if installed)

Phase 7: Post-Deploy Verification

/bug-report verify [BUG-ID] → if VERIFIED FIXED → /bug-report close [BUG-ID]. If STILL PRESENT → reopen, assess rollback, escalate. Schedule /retrospective hotfix within 48h.