Comet Entry

/comet only selects an entry. It does not contain either workflow's execution method.

Once this Skill is loaded, treat the /comet entry as selected. Immediately perform the entry resolution below; do not re-evaluate whether the task is suitable for Comet or only explain why Comet will not be used.

1. Run the public Comet CLI installed on PATH in the current project:

   comet workflow resolve . --json
   

2. Parse the JSON. Only accept schema: comet.workflow-resolution.v1 and a skill value listed below. If the command returns command not found, executable not found, or ENOENT, stop and explain that the Comet CLI installation is incomplete. Do not search for Skill files, scan platform configuration directories, or invoke an internal bundle directly. If the CLI starts but exits nonzero, configuration parsing fails, output is not JSON, or a required field is invalid, likewise stop and report the original error without falling back or guessing.

3. Select exactly one entry based only on the returned skill. Immediately use the Skill tool to load that entry, and load no other entry:

   • /comet-native → Execute immediately: Use the Skill tool to load the comet-native skill. Do not skip this step.
   • /comet-classic → Execute immediately: Use the Skill tool to load the comet-classic skill. Do not skip this step.

   After the skill is loaded, pass the user's original request unchanged to the loaded entry Skill as its user input.

Do not switch workflows based on task size, file count, active changes, or model judgment. Native and Classic changes, states, and artifacts always remain independent.