hotfix is a lightweight Comet preset for fixing a clear bug. It runs open -> build -> verify -> archive, skips full brainstorming and planning, but still keeps OpenSpec state, root-cause elimination checks, verification, and archive.
hotfix is not “no process.” It reduces up-front design cost while preserving recovery, verification, and traceability.
hotfix is faster because the design overhead is lower, not because verification and archive disappear.
When to use it
Use hotfix when all of these are true:- You are fixing existing behavior.
- You are not adding a new capability.
- You are not changing public APIs, schemas, or architecture.
- The scope is predictable.
Relationship to full and tweak
Flow
Default state
comet-state init <name> hotfix defaults to:
At entry, hotfix pauses once and asks you to explicitly keep the current branch, create a branch, or create a worktree; it no longer silently selects an isolation mode. The confirmed
isolation and bound_branch describe the real execution workspace, and later accidental branch switches are blocked. tdd_mode: direct skips Red-Green-Refactor but still requires relevant tests and regression evidence.
Root-cause check
This is hotfix-specific. Before build exits, Comet checks that the proposal’s described root cause has actually been removed. If not, it stays in build and continues fixing.Upgrade signals
Comet pauses when it sees qualitative signals such as cross-module coordination, new capability, schema change, new public API, or deep architecture issue. File-count thresholds are tripwires for user confirmation, not automatic full-workflow upgrades. Upgrade through the legal transition:Recovery
Hotfix is idempotent. After interruption, run/comet. When configuration selects Classic, the internal /comet-classic router reads .comet.yaml and returns to /comet-hotfix when the change is in phase: build.