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

# Adopt Comet in an existing project

> Add Comet to an existing repository by understanding component detection, overwrite behavior, and migration paths.

## Short path

```bash theme={null}
cd existing-project
comet init
```

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

## What `comet init` does

Comet checks for existing OpenSpec, Superpowers, Comet, platform Skill, rule, and hook files. It reports what exists and asks before replacing user-owned files.

## Four common scenarios

### Plain codebase

Use `comet init`, then start with `/comet your change`.

### Already using OpenSpec

Comet can reuse the spec structure and add workflow orchestration around it.

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

Ask `/comet` to inspect the active OpenSpec change. Comet should create workflow state that points at the existing change instead of making a duplicate.

## Upgrade an existing Comet install

```bash theme={null}
npm install -g @rpamis/comet@latest
comet update
comet doctor
```

## Checklist after adoption

* `comet status` works.
* `comet doctor` has no blocking errors.
* Your AI coding tool can see `/comet`.
* Project-level files are committed if the team should share them.