comet-hotfix
Comet Preset: Hotfix
Before starting or resuming, read and follow comet-classic/reference/classic-layout.md. All OpenSpec CLI calls must use the adapter, and all paths must use the bound <classic-*> logical roots.
A short defect-repair flow: open → build → root cause check → verify → archive. It skips brainstorming and a full implementation plan, and applies to repairing existing behavior without designing new features.
All applicability conditions must hold:
- Repair an existing feature's defect without adding a feature.
- No interface changes or architectural redesign.
- The scope can be estimated. File counts are only a prompt for review, not an automatic escalation rule; see “Escalation decisions.”
When the preset may no longer fit: If the repair encounters changes listed under “Escalation decisions,” let the user decide whether to use the full /comet-classic flow.
On first entering a phase, handing off to a new Agent, or restoring context, read and follow Task Context and Artifact Language. Prefer the current continuation or claimed Action's contextRequest; do not retrieve repeatedly during uninterrupted work in the same phase.
Personal memory contains reusable user information, never task summaries, progress, command output, or test results.