/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:
/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 ....
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.
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:
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.
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:
status and show never change selection as a side effect.
Continue with User decisions and clarification protocol and Continuation and checkpoints.