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

Stages
- Understand the target Skill.
- Read project preferences.
- Discover candidate Skills from real local sources.
- Present a confirmation plan.
- Initialize draft metadata after confirmation.
- Generate the package.
- Complete authoring lanes.
- Run eval evidence.
- Review readiness.
- Approve and publish.
- Preview distribution.
- 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