> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comet.rpamis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Auto-transition

> Understand how Comet automatically advances between phases, when it stops, and how auto_transition changes handoff behavior.

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.

<p align="center">
  <img src="https://mintcdn.com/comet-bb5f5294/piE9AoWsM20071ec/assets/auto-transition-illustrations/01-phase-vs-next.png?fit=max&auto=format&n=piE9AoWsM20071ec&q=85&s=933effc599071b37907c71f2e78db2c8" alt="Xiaoyu pushes phase beads through a guard while the auto_transition switch controls the next handoff" width="800" data-path="assets/auto-transition-illustrations/01-phase-vs-next.png" />
</p>

## 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. |

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, 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

* [Decision points](/en/concepts/decision-points)
* [Workflow concepts](/en/concepts/workflow)
* [comet-state](/en/scripts/comet-state)