auto-hotfix

To create a hotfix spec for urgent production issues, draft an autonomous specification assigning a HOTFIX-NNN id, defining the smallest viable fix, rollback plan, and post-fix follow-ups. The system outputs this rollback-ready spec into tasks/active with clear branch guidance for fast execution.

A rollback-ready hotfix specification is a minimal document generated for urgent production outages, data corruption, or security vulnerabilities. It defines the smallest viable fix, assigns a HOTFIX-NNN id, specifies a rollback plan, and ensures proper spec placement with post-fix follow-ups according to project rules.

To document a minimal scope for a production outage fix, generate a hotfix specification using the hotfix template. The system specifies the smallest viable fix, assigns a unique HOTFIX-NNN id, and includes a rollback plan and post-fix follow-ups to ensure immediate deployment readiness.

Yes, automated hotfix specs support urgent production scenarios including data corruption and security vulnerabilities. The system drafts a minimal, rollback-ready specification with a clear scope, assigns a HOTFIX-NNN id, and outputs it to tasks/active for immediate deployment.

The best way to ensure proper hotfix branch guidance and spec placement is to draft the HOTFIX-NNN specification directly into tasks/active using the hotfix template. The system automatically includes a rollback plan and post-fix follow-ups according to project rules.

You need an autonomous hotfix specification when facing urgent production issues like prod outages, data corruption, or security vulnerabilities. The system produces a minimal, rollback-ready spec with a clear scope for immediate deployment, ensuring proper ID assignment and post-fix follow-ups.