speckit-workflows.hotfix

An emergency hotfix workflow automates the creation of an expedited process for critical incidents, generating a hotfix branch and outlining urgent resolution steps. It mandates post-mortem documentation to prevent recurrence of the issue.

Managing a P0 incident requires an expedited hotfix process that documents the incident and schedules a mandatory post-mortem. This ensures immediate attention for resolution and structured follow-up analysis to prevent future occurrences.

Yes, you need a spec-kit project structure with a .specify/ directory to execute incident management workflow scripts. This directory is required to run the emergency hotfix processes and generate the corresponding incident logs.

Mandatory post-mortem documentation is scheduled automatically after an expedited hotfix deployment to analyze the critical incident. It logs the incident details and outlines structured follow-up steps to prevent recurrence.

No, this expedited process applies specifically to urgent software deployment scenarios requiring immediate attention, such as a critical production service being down. Non-emergency deployments should follow standard workflows.

The hotfix workflow requires a .specify/ directory because it relies on the spec-kit project structure to execute workflow scripts. This directory provides the necessary environment to run the emergency hotfix process and generate incident logs.