comet-classic

Orchestrates OpenSpec and Superpowers phases for structured change development workflows.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-classic-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-classic
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-classic
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-classic-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing multi-phase software changes (proposal, design, build, verify, archive) across OpenSpec and Superpowers tooling is error-prone when agents lose track of state, skip design steps, or resume the wrong change. This Skill provides a deterministic routing and state machine that detects the active change, resolves user intent, and drives each phase with explicit decision points. ## Core Features & Use Cases - Intent routing and phase detection: Builds a CometIntentFrame from the user request and active changes, routes through the intent runtime to hotfix, tweak, full, resume, or ask_user paths. - State-driven workflow: Reads .comet.yaml to determine the current phase (open, design, build, verify, archive) and enforces hard constraints like isolation, build_mode, tdd_mode, and review_mode before transitions. - Blocking decision points: Pauses at ten defined user decision nodes (workflow selection, design confirmation, build settings, archive confirmation, preset upgrades) instead of auto-deciding. - Use Case: A developer says "/comet-classic add rate limiting to the API"; the Skill detects no active change, routes to the full workflow, invokes /comet-open to create OpenSpec artifacts plus .comet.yaml, then advances through design, build, verify, and archive with confirmations at each decision point. ## Quick Start Ask the assistant to start or resume the Comet Classic workflow for your change, for example by invoking /comet-classic with a short description of the change you want to make.

Frequently Asked Questions about comet-classic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a new change with the Comet Classic workflow?▼

Invoke /comet-classic with a description of your change. The Skill runs intent routing, and for a full route it invokes /comet-open, which creates the OpenSpec artifacts plus the .comet.yaml state file before entering the design phase.

How does Comet Classic resume an interrupted change?▼

It reruns active change discovery with comet classic openspec -- list --json, then reads .comet.yaml to detect the phase. File state is treated as the source of truth when metadata conflicts, and execution resumes from the detected phase.

What is the difference between comet-hotfix, comet-tweak, and the full workflow?▼

Hotfix handles bug fixes to existing behavior and tweak handles lightweight single-change work, both skipping brainstorming. The full workflow is required for new capabilities, public API or schema changes, and cross-module work, and includes deep design and planning.

Can the workflow skip user confirmation at decision points?▼

No. Ten defined decision points, such as design confirmation, build settings, and archive confirmation, are blocking. The agent must present options and wait for an explicit user choice before writing state or continuing.

What happens when a hotfix or tweak grows beyond its scope?▼

Qualitative signals like schema changes or new public APIs pause the flow and offer a two-choice decision: continue the preset or upgrade to full. Upgrading uses comet state transition preset-escalate to rewind to design and add a Design Doc.