Adopt Comet Classic in an existing project

Short path

cd existing-project
comet init --workflow classic

Choose project-level install when collaborators should share the workflow.

What Classic initialization does

comet init --workflow classic checks for existing OpenSpec, Superpowers, Comet, platform Skill, rule, and hook files. It reports what exists and asks before replacing user-owned files. For a project-level English install, it also creates a default .comet/config.yaml when one does not exist:

# .comet/config.yaml (Classic only, English Skill selected)
schema: comet.project.v1
default_workflow: classic
workflows:
  - classic
ambient_resume: true
classic:
  artifact_layout: docs
  language: en
  context_compression: off
  review_mode: standard
  auto_transition: true

.comet/config.yaml is project-level configuration. Each change’s .comet.yaml is created by /comet-open, not by init. classic.language is snapshotted into .comet.yaml when a change is created and constrains the primary language of OpenSpec and Superpowers artifacts.

New Classic projects use docs/openspec/ by default. If the repository already has a root-level openspec/, Comet retains it as the legacy layout instead of moving existing changes during initialization or upgrade. To migrate from the legacy layout to docs/openspec/, see Migrate Classic layout.

Four common scenarios

Plain codebase

Use comet init --workflow classic, then start with /comet your change; the shared entry selects Classic from configuration.

Already using OpenSpec

Comet can reuse the root-level openspec/ structure as the legacy layout and add workflow orchestration around it without moving active changes.

Already using Superpowers

Comet can reuse execution practices and add OpenSpec-backed change identity.

Already using both

Comet links the existing pieces and adds state, routing, and recovery.

Existing OpenSpec change without `.comet.yaml`

Invoke /comet and ask it to continue the active OpenSpec change. After configuration selects Classic, the internal router should create workflow state that points at the existing change instead of making a duplicate.

Upgrade an existing Comet install

comet update --self-update
comet doctor

Checklist after adoption

comet status works.
comet doctor has no blocking errors.
Your AI coding tool can see /comet and route it to Classic from configuration.
.comet/config.yaml exists and includes shared entry fields plus the classic: block.
Project-level files are committed if the team should share them.

Understand Comet Classic

Five-phase workflow

Presets

Recovery and troubleshooting

Practical scenarios

Adopt Comet Classic in an existing project

Short path

What Classic initialization does

Four common scenarios

Plain codebase

Already using OpenSpec

Already using Superpowers

Already using both

Existing OpenSpec change without `.comet.yaml`

Upgrade an existing Comet install

Checklist after adoption

​Short path

​What Classic initialization does

​Four common scenarios

​Plain codebase

​Already using OpenSpec

​Already using Superpowers

​Already using both

​Existing OpenSpec change without .comet.yaml

​Upgrade an existing Comet install

​Checklist after adoption

Short path

What Classic initialization does

Four common scenarios

Plain codebase

Already using OpenSpec

Already using Superpowers

Already using both

Existing OpenSpec change without `.comet.yaml`

Upgrade an existing Comet install

Checklist after adoption