Skip to main content
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

Check that the command is available:

​
2. Initialize your project

Enter the project root:
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:
Projects with clear existing Classic state remain Classic. You can also choose a workflow or Native artifact root explicitly:
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.
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.

​
3. Call /comet

Open your agent platform in the project and type:
/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.

A small fish follows the Comet quickstart path through installation, initialization, invocation, and recovery

For a quick start, remember only the short path: install, initialize, invoke /comet, and recover from file-backed state.

​
4. Check state

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

​
5. Resume interrupted work

If the session is interrupted, reopen the project and type:
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

Last modified on August 2, 2026