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

# Single Skill and entry routing

> Understand how /comet enters Native from project configuration and how /comet-native advances through one self-contained Skill.

Native does not split Shape, Build, Verify, and Archive into four Skills, and it does not load OpenSpec, Superpowers, or another external method Skill. One `/comet-native` Skill reads state from disk and carries the change through investigation, clarification, implementation, verification, and archive.

## User entry point

Normally, invoke `/comet`. The entry reads `.comet/config.yaml` and deterministically forwards according to `default_workflow`:

```yaml theme={null}
schema: comet.project.v1
default_workflow: native
workflows:
  - native
  - classic
```

`/comet-native` is the explicit target for routing diagnostics or an intentional Native entry. It is a host Skill invocation, not a shell command. Runtime commands use `comet native ...`.

<Note>
  Comet does not infer the mode from task size, prompt wording, or model name. Change the project configuration to change the default. Selecting another entry does not migrate existing changes.
</Note>

## How one Skill covers four phases

On every entry, the Skill rereads configuration, selection, `comet-state.yaml`, the brief, target specifications, and repository facts, then continues from the current phase:

| Phase   | Skill responsibility                                                                                      |
| ------- | --------------------------------------------------------------------------------------------------------- |
| Shape   | Investigate facts, resolve user decisions, and establish the brief and complete target specifications     |
| Build   | Let the model choose implementation methods and submit real project artifacts as the implementation scope |
| Verify  | Run checks based on acceptance and risk, then record itemized evidence                                    |
| Archive | Run a two-step preflight, update canonical specs, and archive the change                                  |

Transitions return a structured `continuation`. Only `continue` proceeds in the current invocation. `await-user`, `blocked`, `manual`, and `done` respectively wait for a decision, require remediation, stop autonomous repair, or finish.

<p align="center">
  <img src="https://mintcdn.com/comet-bb5f5294/A7fDsLoRlesBiCJd/assets/native-illustrations/02-single-skill-routing.png?fit=max&auto=format&n=A7fDsLoRlesBiCJd&q=85&s=2826bd26a0cce4209985b3b002d0ef81" alt="Xiaoyu turns to the bookmarked current page of a notebook beside a /comet entry sign, showing one Skill continuing from state" width="1672" height="941" data-path="assets/native-illustrations/02-single-skill-routing.png" />
</p>

## Write ownership

`.comet/current-change.json` records which workflow and change owns the next write. A project installs one shared Hook Router, and one atomic write is routed to at most one Guard. With multiple active changes, select the target explicitly:

```bash theme={null}
comet native select <change-name>
```

Read-only `status` and `show` never change selection as a side effect.

Continue with [User decisions and clarification protocol](/en/native/decision-ownership) and [Continuation and checkpoints](/en/native/continuation-and-checkpoints).