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

# Quickstart

> Install Comet, initialize Native or Classic, and use /comet to enter the workflow configured for the project.

This page covers the shortest path: install the CLI, initialize a project with Native as the default, and invoke `/comet` from an agent platform.

## Prerequisites

* Node.js 22 or newer
* npm or npx
* Git
* A supported AI coding platform, such as Claude Code, Codex, Cursor, Gemini CLI, OpenCode, or ZCode

## 1. Install the CLI

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

Check that the command is available:

```bash theme={null}
comet --version
```

## 2. Initialize your project

Enter the project root:

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

A project-scope initialization asks you to choose the Skill language and target platforms, then enables Native by default for a new Comet project. Native installs only Comet-owned capabilities and creates:

```text theme={null}
.comet/config.yaml
comet/
```

Projects with clear existing Classic state remain Classic. You can also choose a workflow or Native artifact root explicitly:

```bash theme={null}
comet init --workflow native --root docs
comet init --workflow classic
comet init --workflow both
comet init --scope global --workflow native
comet init --scope global --workflow both
```

Only Classic installs or configures OpenSpec, Superpowers, and CodeGraph. Project-level Native, Classic, and both installs each receive one Comet workflow Rule; platforms with Hook support receive one shared Router that selects the Guard for the current change.

<Info>
  A project-scope installation records the project's default workflow, making it suitable for teams.
  A global installation lets you choose which Native or Classic capabilities are available globally,
  but it does not choose a default workflow for any project. In non-interactive global installs,
  omit `--workflow` to keep the Classic default.
</Info>

## 3. Call `/comet`

Open your agent platform in the project and type:

```text theme={null}
/comet add avatar uploads to the user profile
```

`/comet` does not guess which workflow to use. It reads `.comet/config.yaml`, deterministically forwards to `/comet-native` or `/comet-classic`, and preserves the original request in full. Native creates its own change and uses Shape → Build → Verify → Archive to manage requirements, complete target specifications, evidence, and archive, while leaving implementation methods to the strong model.

```mermaid theme={null}
flowchart TD
  A["/comet user goal"] --> B["Read .comet/config.yaml"]
  B -->|native| N["/comet-native"]
  B -->|classic| C["internally enter /comet-classic"]
  N --> NS["Shape → Build → Verify → Archive"]
  C --> CS["open → design → build → verify → archive"]
```

<p align="center">
  <img src="https://mintcdn.com/comet-bb5f5294/piE9AoWsM20071ec/assets/quickstart-illustrations/01-first-run-path.png?fit=max&auto=format&n=piE9AoWsM20071ec&q=85&s=b08416461c753378c5c446eeb65afa1b" alt="A small fish follows the Comet quickstart path through installation, initialization, invocation, and recovery" width="800" data-path="assets/quickstart-illustrations/01-first-run-path.png" />
</p>

<p align="center">
  For a quick start, remember only the short path: install, initialize, invoke `/comet`, and recover
  from file-backed state.
</p>

## 4. Check state

Run this at any time:

```bash theme={null}
comet status
```

You will see the default entry point and separate sections for Native, Classic, and unmanaged OpenSpec changes. If the state looks abnormal, then run:

```bash theme={null}
comet doctor
```

## 5. Resume interrupted work

If the session is interrupted, reopen the project and type:

```text theme={null}
/comet continue
```

Comet resolves the project's default workflow first, then continues from that workflow's change and runtime evidence. It does not cross into the other workflow.

## Next steps

* For the lightweight strong-model flow, see [Native workflow](/en/concepts/native-workflow).
* For the classic five-phase constrained flow, see [Classic workflow concepts](/en/concepts/workflow).
* For quick fixes, see the [hotfix preset](/en/presets/hotfix).