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

# comet bundle

> Understand the advanced Bundle backend command and how it differs from /comet-any and comet publish.

## When to use it directly

Most users should use `/comet-any`, `comet creator`, and `comet publish`. Use `comet bundle` directly only when you are debugging or automating the lower-level package pipeline.

## Common backend phases

| Phase       | Purpose                              |
| ----------- | ------------------------------------ |
| draft       | Create or update bundle draft state. |
| compile     | Produce generated package files.     |
| eval-plan   | Prepare evaluation metadata.         |
| eval-record | Attach eval evidence.                |
| review      | Inspect candidate readiness.         |
| publish     | Prepare distribution metadata.       |

## Skill Creator commands moved to `comet creator`

User-facing creation and resume flows belong under `comet creator`. `comet bundle` remains the advanced backend surface.

## Bundle and publish relationship

Bundle produces the package candidate. Publish decides whether that candidate is ready for distribution.