Skip to main content
Comet can continue from one phase to the next when the current phase has passed its guard and no user decision is required. This keeps routine work moving while preserving explicit pauses at risk points.

Xiaoyu pushes phase beads through a guard while the auto_transition switch controls the next handoff

​
What auto-transition does

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 to comet-state next, so configuration and current state decide the handoff.

​
Next steps

Last modified on August 21, 2026