Compressed workflow for urgent production fixes: diagnose → coder → [tester | reviewer] → consolidate → document. No refactor. No architecture phase unless the issue is not locally fixable.
Execute hotfix for: $ARGUMENTS
Use only when production is broken and fast restoration matters more than broader improvement.
Skips explorer, architect, and refactor only if:
If root cause is unclear, blast radius grows, or fix requires design trade-offs, STOP and use /full-workflow instead.
These always require /full-workflow:
Hotfix IS valid for:
orchestrator → diagnose → coder → [ tester | reviewer ] → consolidate → document
Before calling coder, confirm the root cause. The orchestrator does this directly.
/full-workflow if:
Use coder with: confirmed root cause, target files, instruction for smallest fix.
In parallel: tester (Normal mode, full suite) + reviewer
| Tester | Reviewer | Action |
|---|---|---|
| PASS | APPROVED | Done → Step 5 |
| PASS | NEEDS_CHANGES | Fix loop (1 max) |
| FAIL | APPROVED | Fix loop (1 max) |
| FAIL | NEEDS_CHANGES | Merge → fix loop (1 max) |
On fix loop iteration, revalidate in parallel (tester Fix-loop mode + reviewer), same as Step 3.
Max 2 iterations. If not clean → STOP and escalate to user with:
/full-workflow (if fix is on right track but needs more work)[WIP] marker and explain what remainsAppend to appropriate lessons-{domain}.md:
### [YYYY-MM-DD] Hotfix: <short title>
- **Root cause:** [1-2 sentences]
- **Fix:** [what was changed]
- **Files:** [list]
- **Lesson:** [what to watch for to prevent recurrence]
Follow-up assessment: If root cause reveals systemic issue, suggest /explore-and-plan for structural fix.