Normally, users only invoke /comet. It reads .comet/config.yaml and deterministically enters Native or Classic according to project configuration. When Classic is selected, it forwards internally to the permanent /comet-classic entry point, which splits a change into open, design, build, verify, and archive. Native and Classic changes, state, and artifacts remain independent.
Classic connects OpenSpec and Superpowers into a recoverable workflow. /comet-classic includes intent recognition and rereads active changes, .comet.yaml, and actual file state to decide whether to create, resume, enter a lightweight preset, or invoke the current phase Skill. Users do not need to determine the current phase first.
Classic primarily targets model capability tiers below Fable 5 and GPT-5.6. For these models, explicit Spec, design, planning, TDD, debugging, and review phases reduce omissions and process drift. Comet’s existing real-model baseline has shown that these constraints can maintain good task coverage and completion at lower capability tiers. Fable 5, GPT-5.6, and similarly capable models are generally better suited to the lighter-method Native workflow. Model names are selection guidance; Comet does not inspect the model and switch modes automatically.
What matters most
Why connect OpenSpec and Superpowers
OpenSpec is strong at change identity: proposals, deltas, tasks, and archive history.
Superpowers is strong at execution depth: brainstorming, design docs, implementation plans, TDD, review, and verification discipline.
Comet keeps both roles explicit:
The five phases
Handoff hash
A handoff hash records the design-to-build contract. It is recalculated from selected artifacts so Comet can detect when the spec, design, or tasks changed underneath the current phase.
Spec scope
Comet distinguishes the main spec from delta specs. Delta specs describe the current change. Archive promotes accepted deltas into long-term spec history.
How Classic chooses a phase entry point
After /comet forwards to /comet-classic, Classic reads project files and classifies the request against current state. It can start a new change, resume the current one, route a status request, enter a lightweight preset, or ask for a decision when the next step is unsafe to infer.
Lightweight presets
Use hotfix for narrow urgent fixes and tweak for small low-risk changes. Either preset can upgrade into the full workflow when risk increases. Last modified on July 22, 2026
