Skip to main content
The /comet-any workflow is long because it creates a reviewable and distributable Skill package, not just a prompt file.

Xiaoyu folds the /comet-any long chain into planning, generation, eval evidence, review, publish, and distribution sections

Stages

  1. Understand the target Skill.
  2. Read project preferences.
  3. Discover candidate Skills from real local sources.
  4. Present a confirmation plan.
  5. Initialize draft metadata after confirmation.
  6. Generate the package.
  7. Complete authoring lanes.
  8. Run eval evidence.
  9. Review readiness.
  10. Approve and publish.
  11. Preview distribution.
  12. Distribute to target platforms.

Key evidence

plan.json structure

The main input in plan.json is workflow (the Workflow Contract):

Comet-native Skill generation

/comet-any assembles artifacts through authoring lanes. Generated output includes the entry SKILL.md, internal Skills for each Workflow Node, and:
  • reference/workflow-protocol.json — the single runtime source of truth for nodes, edges, Output Schema, state, and evals
  • reference/resolved-skills.json — real Skill source evidence and workflow node bindings
  • comet/eval.yaml — the eval manifest used before publishing

Next steps

Last modified on July 6, 2026