hotfix

Automated incident response files a structured incident with a unique slug and YAML frontmatter, dispatching a constrained hotfix-responder subagent to execute fixes while recording gates bypassed and completion status for end-to-end auditability.

Use a rapid hotfix workflow during production outages when standard spec-to-build ceremonies are too slow. It provides speed by dispatching a single authorized responder while preserving an auditable trail of touchpoints and bypassed gates.

Yes, incident response automation can preempt in-flight build waves when necessary. It enforces one active incident at a time and surfaces a postmortem debt banner to signal required follow-up actions and long-term learning.

Track incident fixes by maintaining an auditable trail of gates bypassed, completion status, and touchpoints. The system automatically proposes a postmortem once the incident is resolved, ensuring post-incident review accountability.

Run the hotfix command with a brief incident description to begin the incident-response lane and trigger a single-dispatch hotfix-responder subagent operating under strict gate controls.

No, the system enforces one active incident at a time to ensure accountability. It dispatches a single authorized hotfix-responder subagent under strict gate controls, preventing concurrent unmanaged incident fixes.