hotfix

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Goal

Execute expedited emergency response workflow for critical production issues requiring immediate resolution.

Key Principles:

1. Speed First: Minimal process overhead, maximum velocity
2. Safety: Despite speed, maintain essential safeguards
3. Rollback Ready: Always have rollback plan
4. Post-Mortem: After fire is out, analyze and learn
5. Communication: Keep stakeholders informed

Use Cases: Critical bugs, security vulnerabilities, data corruption, service outages

Coverage: Addresses ~10-15% of development work (emergencies)

---

Smart Integration Detection

# Check for SpecSwarm (tech stack enforcement) - OPTIONAL in hotfix
SPECSWARM_INSTALLED=$(claude plugin list | grep -q "specswarm" && echo "true" || echo "false")

# Check for SpecTest (parallel execution, hooks, metrics)
SPECTEST_INSTALLED=$(claude plugin list | grep -q "spectest" && echo "true" || echo "false")

# In hotfix mode, integration is OPTIONAL - speed is priority
if [ "$SPECTEST_INSTALLED" = "true" ]; then
  ENABLE_METRICS=true
  echo "🎯 SpecTest detected (metrics enabled, but minimal overhead)"
fi

if [ "$SPECSWARM_INSTALLED" = "true" ]; then
  TECH_VALIDATION_AVAILABLE=true
  echo "🎯 SpecSwarm detected (tech validation available if time permits)"
fi

Note: In hotfix mode, speed takes precedence. Tech validation and hooks are OPTIONAL.

---

Pre-Workflow Hook (if SpecTest installed)

if [ "$ENABLE_METRICS" = "true" ]; then
  echo "🎣 Pre-Hotfix Hook (minimal overhead mode)"
  WORKFLOW_START_TIME=$(date +%s)
  echo "✓ Emergency metrics tracking initialized"
  echo ""
fi