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.
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.
| Result | Meaning |
|---|
NEXT: auto | Continue into the next Skill. |
NEXT: manual | Stop and show the next command. |
NEXT: done | Workflow is complete. |
auto_transition setting
auto_transition lives in .comet/config.yaml and is snapshotted into new changes.
| Value | Behavior |
|---|
true | Continue automatically when safe. |
false | Stop at phase boundaries and print the next command. |
Always-stop points
Comet must stop for proposal/design/task review, PRD splitting, build-mode choices, verification failure decisions, branch handling, archive 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 July 1, 2026
