/comet-classic reads the current phase, advances state, and selects the next Skill. This page explains that sequence and how recovery behaves around it.
Phase advancement and handoff
After a phase completes, Comet runs the phase guard. If the guard passes,comet-state next decides whether the next step is automatic, manual, or done.
auto_transition setting
classic.auto_transition lives in .comet/config.yaml and is snapshotted into new Classic changes as auto_transition.
Decision points always stop regardless of this setting.
Always-stop points
Comet must stop for proposal/design/task review, PRD splitting, build-mode choices, verification failure decisions, the combined archive-and-delivery confirmation, and preset upgrade decisions.Why this matters
The agent does not hardcode the next Skill. It delegates tocomet-state next, so configuration and current state decide the handoff.
Next steps
- Decision points
- Classic configuration —
auto_transitionand configuration precedence - Workflow concepts
- comet-state