---
description: Emergency fix with fast-track severity routing
argument-hint: <description> [--severity critical|high] [--rationale <why>] [#tag1 #tag2]
model: claude-sonnet-4-6
---

Log an emergency fix to both CHANGELOG.md and blockers.md with HOTFIX marker. Fast-tracks QA → Security → DevOps.

Use ONLY for production incidents, security patches, data loss prevention. NOT for "this was urgent so I shipped it."

Args: $ARGUMENTS

## Input

- `description`: What was fixed (e.g., "Fixed payment processing timeout")
- `severity`: critical (data loss, security breach) or high (outage, core feature broken)
- `rationale`: Why it was critical (optional but recommended)
- `#tags`: Domain tags (#api, #security, #infra, #payment, etc.)

## Behavior

1. Append HOTFIX entry to CHANGELOG.md with [HOTFIX] marker
2. Append blocker entry to blockers.md with severity + in-progress status
3. Sync MANIFEST counters

## Output (ultra)

```
✓ Hotfix logged and fast-tracked | severity=<level>
```
